[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fwd: The GNU C Library version 2.28 is now available

From: David Michael
Subject: Re: Fwd: The GNU C Library version 2.28 is now available
Date: Wed, 1 Aug 2018 18:05:50 -0400

On Wed, Aug 1, 2018 at 11:37 AM, Samuel Thibault
<samuel.thibault@gnu.org> wrote:
> About glibc repositories, we should upgrade the Hurd glibc repository to
> 2.28, when would that be fine for people using it? (I'm thinking about
> Guix & Arch people)

Now that there is an upstream release with the Hurd patches (thanks
for doing that), my preference as a user would be to switch from the
Savannah repo to the upstream release tarball and apply any individual
patches required by Hurd as they pop up.

Do you think Hurd-specific patches are appropriate to send to
libc-stable for backporting to the upstream release branches?

If not, could the Savannah repo maybe have a new branch started on the
release tag that is just for cherry-picking Hurd-specific commits?
The tschwinge/Roger_Whittaker branch can be a bit unwieldy for picking
out patches, and that flat commit topology from cherry-picking is used
for stable branches in other projects like glibc, Linux, and systemd,
which is friendlier to packagers using simple Git commands or the
repo's web interface.  I realize the topgit-managed branch has a
different goal, so a new branch like this would not be intended to
replace it.  If you think this is worth doing, I can volunteer to do
the actual cherry-picking and conflict resolution for the latest glibc
release so it's not putting more of a maintenance burden on you.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]