From: Jim Wilson <wilson@cygnus.com>
To: Fergus Henderson <fjh@cs.mu.oz.au>, Sam TH <sam@uchicago.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: cvs (was: Bootstrap failure of gcc-ss-20010409 in ia64)
Date: Sat, 14 Apr 2001 22:20:00 -0000 [thread overview]
Message-ID: <200104150520.WAA06280@wilson.cygnus.com> (raw)
In-Reply-To: <20010415012749.C1127@hg.cs.mu.oz.au>
> update -d -P
I'm aware of -d, but it isn't appropriate for all cases.
If you used a module to check out a subset of a repository, then using update
-d will give you files that were not part of the module that you checked out.
This isn't really a problem with the FSF gcc repository, since the gcc module
is the entire repository. It is a problem for other repositories that I use,
for instance the combined gdb/binutils repository on sources.redhat.com. If
I check out the binutils module, and then update it, I don't want update to
check out gdb files. Thus I can't use -d.
Also, -d gives you new directories, but it doesn't give you new files.
This matters if you checked out a module that includes specific filenames
in addition to directory names. If someone later modifies the module to
include additional filenames, then update -d will not give you those additional
filenames. This isn't a problem for the FSF gcc repository, since we aren't
using modules that way, but it is a problem for other repositories that I use.
Neither problem exists if you use co instead of update. Thus it is always
better to use co instead of update -d. However, this does require you to
remember to do a co occasionally. For people that don't use as many CVS
features I do, which is probably most people, update -d will work fine.
Jim
next prev parent reply other threads:[~2001-04-14 22:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 6:56 Bootstrap failure of gcc-ss-20010409 in ia64 Andreas Schwab
2001-04-11 12:47 ` Jim Wilson
2001-04-11 17:31 ` Mark Mitchell
2001-04-11 17:43 ` Mark Mitchell
2001-04-11 18:28 ` Daniel Berlin
2001-04-11 18:34 ` Mark Mitchell
2001-04-11 20:24 ` Daniel Berlin
2001-04-11 21:19 ` Mark Mitchell
2001-04-11 21:36 ` Daniel Berlin
2001-04-12 12:27 ` Bill Nottingham
2001-04-12 15:03 ` Daniel Berlin
2001-04-12 21:07 ` Bill Nottingham
2001-04-12 21:46 ` Daniel Berlin
2001-04-12 13:04 ` Jim Wilson
2001-04-12 15:06 ` Daniel Berlin
2001-04-13 8:49 ` Andreas Schwab
2001-04-13 10:04 ` Daniel Berlin
2001-04-13 10:23 ` Andreas Schwab
2001-04-13 12:20 ` Daniel Berlin
2001-04-13 12:39 ` Andreas Schwab
2001-04-13 12:56 ` Daniel Berlin
2001-04-13 13:06 ` Andreas Schwab
2001-04-13 19:13 ` Jim Wilson
2001-04-13 19:59 ` Jim Wilson
2001-04-14 2:01 ` Jim Wilson
2001-04-14 4:08 ` Sam TH
2001-04-14 8:27 ` cvs (was: Bootstrap failure of gcc-ss-20010409 in ia64) Fergus Henderson
2001-04-14 11:28 ` Sam TH
2001-04-14 22:20 ` Jim Wilson [this message]
2001-04-14 23:48 ` Russ Allbery
2001-04-16 15:39 ` Bootstrap failure of gcc-ss-20010409 in ia64 Jim Wilson
2001-04-16 17:22 ` Mark Mitchell
2001-04-16 17:45 ` Jim Wilson
2001-04-17 8:22 ` Mark Mitchell
2001-04-17 8:57 ` Daniel Berlin
2001-04-17 11:01 ` Jim Wilson
2001-04-17 15:38 ` Mark Mitchell
2001-04-17 16:16 ` Daniel Berlin
2001-04-17 16:36 ` Mark Mitchell
2001-04-18 14:35 ` debugging optimized programs (Was: Re: Bootstrap failure of gcc-ss-20010409 in ia64) Joern Rennecke
2001-04-18 15:12 ` Daniel Berlin
2001-04-18 15:49 ` Joern Rennecke
2001-04-18 17:06 ` Daniel Berlin
2001-04-18 17:18 ` Daniel Berlin
2001-04-18 12:41 ` Bootstrap failure of gcc-ss-20010409 in ia64 Jim Wilson
2001-04-18 13:49 ` Mark Mitchell
2001-04-18 14:34 ` Jim Wilson
2001-04-18 15:31 ` 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=200104150520.WAA06280@wilson.cygnus.com \
--to=wilson@cygnus.com \
--cc=fjh@cs.mu.oz.au \
--cc=gcc@gcc.gnu.org \
--cc=sam@uchicago.edu \
/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).