[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Upstreaming the glibc Hurd port
From: |
Samuel Thibault |
Subject: |
Re: Upstreaming the glibc Hurd port |
Date: |
Thu, 18 Jan 2018 18:00:23 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
Joseph Myers, on jeu. 18 janv. 2018 16:47:55 +0000, wrote:
> On Thu, 18 Jan 2018, Samuel Thibault wrote:
> > Not all of them are necessary for managing to build glibc. Some of them
> > are just hacking, others are perhaps almost ready to commit, just
> > missing changelogs & formatting. That's the triaging thing that takes
> > time, and having to do all the work including changelogs & formatting
> > makes it get lower in my global TODOlist.
>
> I'm still arguing on bug-standards for removing the requirement for
> ChangeLog format (given a public distributed version control system), but
> that wouldn't remove the requirement for proper explanations of patches,
Thomas: this is were your help should be focused. Some of your branches
only have "WIP", which is not helpful to know what you were hacking when
writing them.
Samuel
- Re: Upstreaming the glibc Hurd port, (continued)
- Re: Upstreaming the glibc Hurd port, Samuel Thibault, 2018/01/23
- Re: Upstreaming the glibc Hurd port, Joseph Myers, 2018/01/23
- Re: Upstreaming the glibc Hurd port, Samuel Thibault, 2018/01/23
- Re: Upstreaming the glibc Hurd port, Samuel Thibault, 2018/01/24
- Re: Upstreaming the glibc Hurd port, Joseph Myers, 2018/01/25
- Re: Upstreaming the glibc Hurd port, Joseph Myers, 2018/01/25
- Re: Upstreaming the glibc Hurd port, Samuel Thibault, 2018/01/25
- Re: Upstreaming the glibc Hurd port,
Samuel Thibault <=
Re: Upstreaming the glibc Hurd port, Samuel Thibault, 2018/01/18
Re: Upstreaming the glibc Hurd port, Florian Weimer, 2018/01/18