This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Question regarding patchwork patches
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Lukasz Majewski <lukma at denx dot de>
- Cc: Paul Eggert <eggert at cs dot ucla dot edu>, 'GNU C Library' <libc-alpha at sourceware dot org>
- Date: Wed, 13 Feb 2019 15:24:11 +0000
- Subject: Re: Question regarding patchwork patches
- References: <20190205102710.66238f9d@jawa> <9d194cb1-ce4c-c95c-215d-279d5a2a4574@cs.ucla.edu> <20190213084906.034b5d82@jawa>
On Wed, 13 Feb 2019, Lukasz Majewski wrote:
> Please forgive me the question - as I'm not experienced with glibc
> development - but is there any time frame (plan) for review(s)?
Submitters are expected to ping their patches weekly. Patchwork is simply
one tool some submitters may choose to use to keep track of the patches
they need to ping.
https://sourceware.org/glibc/wiki/Contribution%20checklist#Ping_and_Keep_Pinging
Note that when pinging you should consider whether the patch is still
appropriate as-is or needs updates and reposting. (For example, a patch
from a previous year adding new files needs copyright date updates; a
patch from a previous development cycle adding new public symbols needs
symbol version updates.)
--
Joseph S. Myers
joseph@codesourcery.com