On Wed, Aug 1, 2018 at 6:10 PM, Samuel Thibault <samuel.thiba...@gnu.org> wrote: > David Michael, le mer. 01 août 2018 18:05:50 -0400, a ecrit: >> On Wed, Aug 1, 2018 at 11:37 AM, Samuel Thibault >> <samuel.thiba...@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? > > I don't know actually. My wild guess is that upstream will be fine to > backport anything we feel is really needed, as long as it is limited to > Hurd code. For more invasive changes, it would make sense to have a > branch in the hurd repo with normal, non-topgit, cherry-picks.
Okay, that makes sense. I'd be interested to try such a branch and see how it works out (once new Hurd patches are available, of course). If you would like help maintaining it, I'm not currently in the Savannah project, but my username is dm0 there in case it can be given permission. I'd assume the branch would follow the usual rule of other projects' stable branches, where only cherry-picks of patches already applied in master are allowed. Thanks. David
