public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/5414: Suggest using -z1 option for cvs in contrib/gcc_update
Date: Thu, 17 Jan 2002 21:36:00 -0000 [thread overview]
Message-ID: <20020118053600.9562.qmail@sources.redhat.com> (raw)
The following reply was made to PR other/5414; it has been noted by GNATS.
From: Craig Rodrigues <rodrigc@mediaone.net>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, georg.wild@gmx.de,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: other/5414: Suggest using -z1 option for cvs in contrib/gcc_update
Date: Fri, 18 Jan 2002 00:27:08 -0500
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5414
The instructions at http://gcc.gnu.org recommend using -z 9, so would
this
be acceptable to add to gcc_update?
Index: gcc_update
===================================================================
RCS file: /cvs/gcc/gcc/contrib/gcc_update,v
retrieving revision 1.33
diff -u -r1.33 gcc_update
--- gcc_update 2001/11/07 20:26:58 1.33
+++ gcc_update 2002/01/18 05:26:40
@@ -212,7 +212,7 @@
fi
echo "Updating CVS tree"
-cvs -q update ${1+"$@"}
+cvs -z 9 -q update ${1+"$@"}
if [ $? -ne 0 ]; then
(touch_files_reexec)
echo "CVS update of full tree failed." >&2
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@mediaone.net
next reply other threads:[~2002-01-18 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 21:36 Craig Rodrigues [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-19 14:26 rodrigc
2002-01-18 7:36 Geoff Keating
2002-01-17 9:06 georg.wild
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=20020118053600.9562.qmail@sources.redhat.com \
--to=rodrigc@mediaone.net \
--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).