GLIBC 2.23 Update Translations
Joseph Myers
joseph@codesourcery.com
Thu Feb 18 21:56:00 GMT 2016
On Thu, 18 Feb 2016, Mike Frysinger wrote:
> On 18 Feb 2016 17:55, Adhemerval Zanella wrote:
> > Due an overlook in the wiki release from my part I created the release tag
> > without updating both libc.pot and the translation po. So I am aiming the
> > correct translation update to 2.23.1. I also updated both on master and
> > already backported on the 2.23 branch.
> >
> > The question is: are there enough changes to warrant a 2.23.1 with
> > translation updates so people can use those tarballs?
>
> have tarballs been generated ? deleting/rewriting tags are generally
> harmless in git (unlike branches) because you don't really branch from
> a tag, and when you `git pull` it'll just force update.
I don't think git pull will update a tag that gets moved.
--
Joseph S. Myers
joseph@codesourcery.com
More information about the Libc-alpha
mailing list