From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: jsm28@cam.ac.uk
Cc: gcc@gcc.gnu.org
Subject: Re: gcc-ss-20011203 is now available
Date: Tue, 04 Dec 2001 08:17:00 -0000 [thread overview]
Message-ID: <10112041611.AA16876@vlsi1.ultra.nyu.edu> (raw)
Could people please ensure that they commit each logical patch (such
that users should not try to build an intermediate state) in a single
commit with all relevant files named on the command line?
I certainly agree with that. However, it is important to point out that it's
not always possible to put them all on the command line due to command-line
length restrictions on some systems. I've run into that myself once a
few months ago.
So this sort of inconsistency is inevitable, though hopefully rare.
next reply other threads:[~2001-12-04 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 8:17 Richard Kenner [this message]
2001-12-04 8:32 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2001-12-03 19:13 gccadmin
2001-12-04 7:11 ` Andreas Schwab
2001-12-04 7:59 ` Joseph S. Myers
2001-12-04 12:16 ` guerby
2001-12-04 12:24 ` Joseph S. Myers
2001-12-04 12:30 ` Phil Edwards
2001-12-04 12:36 ` Joseph S. Myers
2001-12-04 12:46 ` Phil Edwards
2001-12-04 19:54 ` Mark Mitchell
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=10112041611.AA16876@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
/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).