From: Ulrich Drepper <drepper@redhat.com>
To: DJ Delorie <dj@redhat.com>
Cc: law@redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: Minor change to regex.c
Date: Tue, 13 Nov 2001 15:03:00 -0000 [thread overview]
Message-ID: <m3itcb25x3.fsf@myware.mynet> (raw)
In-Reply-To: <200111151915.fAFJFa227199@greed.delorie.com>
DJ Delorie <dj@redhat.com> writes:
> We're not asking you to actively maintain them, just to let us
> maintain them in the glibc cvs repository.
And let them accumulate bit rot there? That's crap. In glibc the K&R
stuff would never ever be tested and if necessary there will be more
and more non-ISO C changes.
> Otherwise, what's the point of glibc being the master source for
> that file?
Who said that? If the master repository is in glibc this is noted in
the file. This is not the case for regex.
> Or, if you don't want glibc to be the master, then where *is* the
> master that you send your patches to?
I'm maintaining the glibc version. What everybody else does is none
of my business.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
next prev parent reply other threads:[~2001-11-15 19:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 15:03 law
2001-11-13 15:03 ` Ulrich Drepper
2001-11-13 15:03 ` DJ Delorie
2001-11-13 15:03 ` law
2001-11-13 15:03 ` Ulrich Drepper
2001-11-13 15:03 ` Andrey Petrov
2001-11-13 15:03 ` law
2001-11-13 15:03 ` Ulrich Drepper
2001-11-13 15:03 ` DJ Delorie
2001-11-13 15:03 ` Ulrich Drepper [this message]
2001-11-13 15:03 ` DJ Delorie
2001-11-13 15:03 ` Ulrich Drepper
2001-11-13 15:03 ` DJ Delorie
2001-11-13 15:03 ` Ulrich Drepper
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 15:03 Kaveh R. Ghazi
2001-11-13 15:03 Kaveh R. Ghazi
2001-11-13 15:03 ` law
2001-11-13 15:03 ` DJ Delorie
2001-11-13 15:03 ` Andrey Petrov
2001-11-13 15:03 ` DJ Delorie
2001-11-13 15:03 Kaveh R. Ghazi
2001-11-13 15:03 ` DJ Delorie
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=m3itcb25x3.fsf@myware.mynet \
--to=drepper@redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).