This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [COMMITTED] ja_JP: Change the offset for Taisho gan-nen from 2 to 1 [BZ #24162]


Hello Rafal-san,

From: Rafal Luzynski <digitalfreak@lingonborough.com>
Subject: Re: [COMMITTED] ja_JP: Change the offset for Taisho gan-nen from 2 to 1 [BZ #24162]
Date: Wed, 20 Mar 2019 23:08:23 +0100 (CET)

> > Yes, I remember the work remaining to backport this patch to 2.29.
> 
> OK, nice.

I have done git push to 2.29 branch.

https://sourceware.org/bugzilla/show_bug.cgi?id=24162#c10

> But now I can see that this bug is only half-fixed because it mentions the
> BC direction as well.  No reason to mention it as fixed in NEWS then.
> Whether to backport the patch it's up to you, my suggestion is yes,
> backport.

OK.  So, I did not update NEWS file this time.

* Note to self: Steps to backport from master to 2.29

git fetch origin release/2.29/master
git checkout release/2.29/master
git cherry-pick -x 31effac
cat << "EOF" | patch ChangeLog
1,3d0
< <<<<<<< HEAD
< 2019-03-21  Stefan Liebler  <stli@linux.ibm.com>
< =======
10,11c7
< 2019-03-01  Gabriel F. T. Gomes  <gabriel@inconstante.eti.br>
< >>>>>>> 31effacee2... ja_JP: Change the offset for Taisho gan-nen from 2 to 1 [BZ #24162]
---
> 2019-03-21  Stefan Liebler  <stli@linux.ibm.com>
EOF
git add ChangeLog
git cherry-pick --continue
git push origin release/2.29/master

> > By the way, is there a plan to release 2.29.1?
> 
> I asked a similar question before and the answer (if I remember correctly)
> was: no, but distros are free to apply the upstream patches, and some of
> them (e.g., Fedora) do this regularly.

Thank you for your explanation.  Understood.

Regards,
TAMUKI Shoichi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]