[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Glibc port: commit clenup
From: |
Samuel Thibault |
Subject: |
Re: Glibc port: commit clenup |
Date: |
Mon, 19 Feb 2018 19:04:57 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
Svante Signell, on lun. 19 févr. 2018 18:51:12 +0100, wrote:
> I've found the upstream upstream repo thanks. So, what is the
> procedure, create a branch http://git.savannah.gnu.org/cgit/hurd/glibc.
> git/ with one patch per debian patch
See the branches there, they already exist.
> and ask you to commit upstream upstream?
If it was a matter of committing, that'd be done already... See what I
wrote on 18 Jan 2018:
«
Most of them don't have changelog, have formatting issues, etc. That's
what needs to be fixed until we can commit them.
»
Really, just read what has *already* been written.
> How to find out which patches are fixed, and which are
> pending?
See the .topmsg file in the corresponding branch.
Samuel
- Re: Glibc port: commit clenup, Samuel Thibault, 2018/02/17
- Re: Glibc port: commit clenup, Svante Signell, 2018/02/17
- Re: Glibc port: commit clenup, James Clarke, 2018/02/17
- Re: Glibc port: commit clenup, Samuel Thibault, 2018/02/17
- Re: Glibc port: commit clenup, Svante Signell, 2018/02/19
- Re: Glibc port: commit clenup,
Samuel Thibault <=
- Re: Glibc port: commit clenup, Samuel Thibault, 2018/02/19
- Re: Glibc port: commit clenup, Amos Jeffries, 2018/02/19
- Re: Glibc port: commit clenup, Samuel Thibault, 2018/02/20
- Re: Glibc port: commit clenup, Samuel Thibault, 2018/02/20