[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 14:47:37 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
Samuel Thibault, on jeu. 18 janv. 2018 14:40:37 +0100, wrote:
> I came up with the following list of patches
They are usually more or less named like the corresponding topgit branch
in our glibc repo. The .topmsg file can be use to track what work has
been done on the patch (checking formatting, changelog, etc.). Once a
topgit branch is known to be alright, I can commit it very quickly.
Samuel
- Re: Upstreaming the glibc Hurd port, Samuel Thibault, 2018/01/18
- Re: Upstreaming the glibc Hurd port, Samuel Thibault, 2018/01/18
- Re: Upstreaming the glibc Hurd port,
Samuel Thibault <=
- Re: Upstreaming the glibc Hurd port, Joseph Myers, 2018/01/18
- Re: Upstreaming the glibc Hurd port, Joseph Myers, 2018/01/18
- Re: Upstreaming the glibc Hurd port, Samuel Thibault, 2018/01/18
- Re: Upstreaming the glibc Hurd port, Thomas Schwinge, 2018/01/18
- Re: Upstreaming the glibc Hurd port, Samuel Thibault, 2018/01/18
- Re: Upstreaming the glibc Hurd port, Samuel Thibault, 2018/01/18
- Re: Upstreaming the glibc Hurd port, Joseph Myers, 2018/01/18