From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <rittle@labs.mot.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: commitinfo script to check policy, issue warnings (and/or abortcommit)
Date: Fri, 18 May 2001 12:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0105182054180.28875-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <200105181849.f4IIncb90810@latour.rsch.comm.mot.com>
On Fri, 18 May 2001, Loren James Rittle wrote:
> In article < orsni5pu3k.fsf@guarana.lsd.ic.unicamp.br >,
> Alexandre Oliva <aoliva@redhat.com> writes:
>
> > Instead of $*, I'd rather use ${1+"$@"}
>
> I won't even ask why... OK.
I suggest simply using "$@". While robustness in the face of spaces in
filenames is a good idea (although no-one should try to commit such
filenames to the GCC tree), allowing for non-POSIX shells that don't
handle "$@" properly is surely an irrelevance for a script run on
gcc.gnu.org.
Could the script also give a warning if someone commits through the old
"egcs" link rather than the "gcc" directory? I'd like to see these
residual egcs references go away more from gcc-cvs. The script
contrib/newcvsroot allows someone to convert easily.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2001-05-18 12:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 13:54 commitinfo script to check policy, issue warnings (and/or abort commit) Loren James Rittle
2001-05-14 17:45 ` commitinfo script to check policy, issue warnings (and/orabort commit) Mark Mitchell
2001-05-16 0:57 ` commitinfo script to check policy, issue warnings (and/or abort commit) Alexandre Oliva
2001-05-16 1:31 ` commitinfo script to check policy, issue warnings (and/or abortcommit) Gerald Pfeifer
2001-05-18 11:43 ` Loren James Rittle
2001-05-18 11:46 ` Loren James Rittle
2001-05-18 11:40 ` commitinfo script to check policy, issue warnings (and/or abort commit) Loren James Rittle
2001-05-19 18:46 ` Alexandre Oliva
2001-05-20 10:17 ` commitinfo script to check policy, issue warnings (and/orabort commit) Mark Mitchell
2001-05-24 6:15 ` Loren James Rittle
2001-05-16 1:38 ` commitinfo script to check policy, issue warnings (and/or abort commit) Alexandre Oliva
2001-05-18 11:49 ` Loren James Rittle
2001-05-18 12:58 ` Joseph S. Myers [this message]
2001-05-18 13:24 ` commitinfo script to check policy, issue warnings (and/or abortcommit) Loren James Rittle
2001-05-16 6:38 ` Gerald Pfeifer
2001-05-16 9:24 ` commitinfo script to check policy, issue warnings (and/or abort commit) Alexandre Oliva
2001-05-18 12:14 ` commitinfo script to check policy, issue warnings (and/or abortcommit) Loren James Rittle
2001-05-16 13:31 ` commitinfo script to check policy, issue warnings (and/or abort commit) Marc Espie
2001-05-16 15:12 ` Branko
2001-05-17 6:07 ` Marc Espie
2001-05-17 12:08 ` Branko
2001-05-17 20:18 ` Loren James Rittle
2001-05-17 22:22 ` Fergus Henderson
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=Pine.LNX.4.33.0105182054180.28875-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=rittle@labs.mot.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).