From: Petr Vorel <petr.vorel@gmail.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 2/2] package/localedef: bump to version 2.34-9-g9acab0bba6a5a57323b1f94bf95b21618a9e5aa4
Date: Fri, 27 Aug 2021 00:47:05 +0200 [thread overview]
Message-ID: <YSgZ6V/1uWia6lye@pevik> (raw)
In-Reply-To: <4b58e6bf-eb43-facc-2c44-e50ae52ad111@mind.be>
Hi Arnout, all,
> On 22/08/2021 21:22, Petr Vorel wrote:
> > Hi Romain,
> >> Hello Petr,
> >> Le 22/08/2021 à 21:02, Petr Vorel a écrit :
> >>> resync the version with glibc package.
> >>> Dropped 2 patches (fixes backported from previous releases),
> >>> rebased 2 which are kept (only line numbers changed).
> >>> Suggested-by: Romain Naour <romain.naour@gmail.com>
> >>> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> >> Thanks for this new version.
> >> But it will conflict with my patch that resync the glibc version for 2.33
> Resolving those conflicts isn't too difficult, so don't worry about it.
> Well, actually, the "refresh" of the patches *does* make it a bit difficult.
> It's nicer for us if you leave patches untouched as long as they still apply
> correctly.
> >> http://patchwork.ozlabs.org/project/buildroot/patch/20210821131256.1138002-1-romain.naour@gmail.com/
> > OK, I'll rebase it once your commit gets merged.
> > But if bump considered safe, maybe my commits could be taken as it is.
> That's what I did :-)
Thanks!
> >> Since glibc and localedef are really the same project, I would suggest to bump
> >> the version with one commit.
> >> I agree, It's not convenient to take care of localedef package at the same time
> >> of glibc.
> > I was thinking about it as well, but when packages are independent it's IMHO
> > slightly better to split it.
> I don't care much either way - there are arguments for both options. localedef
> and glibc aren't tied that strictly, it's just that glibc changes may result in
> different output of localedef, which you won't notice until you actually use
> those locales at runtime (and then only if you used the changed aspect of it).
> So it's more a just-to-be-safe thing.
Thanks a lot for info.
Kind regards,
Petr
> Regards,
> Arnout
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-26 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 19:02 [Buildroot] [PATCH v2 1/2] package/glibc: bump version to 2.34-9-g9acab0bba6a5a57323b1f94bf95b21618a9e5aa4 Petr Vorel
2021-08-22 19:02 ` [Buildroot] [PATCH v2 2/2] package/localedef: bump to version 2.34-9-g9acab0bba6a5a57323b1f94bf95b21618a9e5aa4 Petr Vorel
2021-08-22 19:17 ` Romain Naour
2021-08-22 19:22 ` Petr Vorel
2021-08-26 21:55 ` Arnout Vandecappelle
2021-08-26 22:47 ` Petr Vorel [this message]
2021-08-26 21:50 ` [Buildroot] [PATCH v2 1/2] package/glibc: bump version to 2.34-9-g9acab0bba6a5a57323b1f94bf95b21618a9e5aa4 Arnout Vandecappelle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YSgZ6V/1uWia6lye@pevik \
--to=petr.vorel@gmail.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox