GLIBC 2.23 Update Translations

[Joseph Myers]

On Thu, 18 Feb 2016, Mike Frysinger wrote:

> On 18 Feb 2016 21:56, Joseph Myers wrote:
> > 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.
> 
> i'm 99.9% sure it does

Not in my testing (unless you use the non-default --tags option to git 
pull to force updates of existing tags).

-- 
Joseph S. Myers
joseph@codesourcery.com