public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/1634: Request for gcc-cvs-patches list
Date: Sat, 11 Jan 2003 20:36:00 -0000 [thread overview]
Message-ID: <20030111203601.18415.qmail@sources.redhat.com> (raw)
The following reply was made to PR other/1634; it has been noted by GNATS.
>From jsm28@cam.ac.uk Mon Jan 13 00:59:45 2003
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>
Subject: Re: other/1634: Request for gcc-cvs-patches list
Date: Sat, 11 Jan 2003 20:33:48 +0000 (GMT)
On Sat, 11 Jan 2003, Nathanael Nerode wrote:
> To what extent is this request superseded by the links in gcc-cvs messages to
> the cvsweb pages giving precisely the corresponding patches?
It isn't. Following hundreds of links a day of the offchance that one
might be wrongly reverting something or wrongly committing something isn't
a reasonable solution to the problem. The idea of this wishlist request
is that the patches themselves go by in email - exactly as committed,
which may differ from how they were sent to gcc-patches, or they may not
have been sent to gcc-patches - for bogus reversions, or bogus changes
(e.g. other changes in the same tree that weren't part of the given patch
and shouldn't have been committed) to be spotted.
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2003-01-11 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 20:36 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-11 21:06 Joseph S. Myers
2003-01-11 20:56 Zack Weinberg
2003-01-11 19:46 Nathanael Nerode
2001-04-01 0:00 Joseph Myers
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=20030111203601.18415.qmail@sources.redhat.com \
--to=jsm28@cam.ac.uk \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).