From: Loren James Rittle <rittle@latour.rsch.comm.mot.com>
To: gcc@gcc.gnu.org
Subject: Re: commitinfo script to check policy, issue warnings (and/or abortcommit)
Date: Fri, 18 May 2001 12:14:00 -0000 [thread overview]
Message-ID: <200105181913.f4IJDux30176@latour.rsch.comm.mot.com> (raw)
In-Reply-To: <Pine.BSF.4.33.0105161536200.33725-100000@taygeta.dbai.tuwien.ac.at>
In article < Pine.BSF.4.33.0105161536200.33725-100000@taygeta.dbai.tuwien.ac.at >,
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
>> 2. Run: cvs import /cvs/gcc SUBVERSION LIBTOOL_RELEASE_NUMBER
>> within the directory populated in step 1.
> Well, as far as I understood, we don't want to absolutely enforce this
> rule, but strongly recommend it, so it would make sense to add such a
> note to codingconventions.html anyway, wouldn't it? Alexandre?
OK, my current understanding is that the idea of using `cvs import' in
the gcc tree has not gone over too well.
> (If Alexandre agrees, I'd say just go ahead and change the web page
> according to your proposal. Thanks!)
Given the feedback, I'm inclined to nix the use of `cvs import'.
Instead, strongly suggest that any change (related to libtool) which
is being checked in must have come from the libtool source base and
that a violation should be corrected ASAP by submitting to the libtool
source base.
I really want to put this thing to bed..
Regards,
Loren
next prev parent reply other threads:[~2001-05-18 12:14 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 ` commitinfo script to check policy, issue warnings (and/or abortcommit) Joseph S. Myers
2001-05-18 13:24 ` 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 ` Loren James Rittle [this message]
2001-05-16 13:31 ` 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=200105181913.f4IJDux30176@latour.rsch.comm.mot.com \
--to=rittle@latour.rsch.comm.mot.com \
--cc=gcc@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).