From: Andreas Jaeger <aj@suse.de>
To: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: Handling of Glibc Patches
Date: Wed, 24 Nov 1999 01:24:00 -0000 [thread overview]
Message-ID: <u8aeo4nszn.fsf@gromit.rhein-neckar.de> (raw)
During the last time I've noticed that different people came up with
patches for the same problem - often even with the same patches.
As a small example, I made this morning a tiny patch to integrate the
two new constants from Linux 2.3.29 - only to find out when I'm ready
with my email that Ulrich has just checked in these patches. I don't
think there was a way to avoid this specific problem at all [1] - but
often there's more time between the submission of the patches and
duplication of work could have been reduced.
The same patches generated by different developers implies a
unnecessary duplication of work. Since the group of core developers
is quite small and most of us don't have that much spare time, we
should reduce this overlap as much as possible.
What can be done to improve the handling of patches?
One solution would be to create a libc-patches list where everybody
would send patches to (similar to gcc-patches). This way we could see
what others have done, comment on the patches and don't duplicate the
work.;-)
What do you think?
Andreas
Footnotes:
[1] Since we worked simultaneously on it.
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de
next reply other threads:[~1999-11-24 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-24 1:24 Andreas Jaeger [this message]
1999-11-24 3:22 ` Mark Kettenis
1999-11-24 8:28 ` Ulrich Drepper
1999-11-24 15:23 ` Philip Blundell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u8aeo4nszn.fsf@gromit.rhein-neckar.de \
--to=aj@suse.de \
--cc=libc-hacker@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).