From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com, xyzzy@hotpop.com
Subject: Re: binutils+gdb CVS module
Date: Mon, 18 Aug 2003 12:56:00 -0000 [thread overview]
Message-ID: <20030818125651.GA20363@nevyn.them.org> (raw)
In-Reply-To: <200308180904.h7I94i9W029387@duracef.shout.net>
On Mon, Aug 18, 2003 at 05:04:44AM -0400, Michael Elizabeth Chastain wrote:
> The normal workaround is to do "cvs update" almost all of the time, with
> no "-d", and to handle new top-level files and directories specially.
> Fortunately they don't appear very often (a few times a year).
The trick is to update directories the same way you checked them out
initially: say "cvs -d <root> co gdb+binutils" from the level above
src, just like the first time. That gets the right set of new files.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-18 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 9:04 Michael Elizabeth Chastain
2003-08-18 10:09 ` Stephen Biggs
2003-08-18 12:56 ` Daniel Jacobowitz [this message]
2003-08-18 13:03 ` Bob Rossi
2003-08-18 14:51 ` Stephen Biggs
2003-08-18 14:54 ` Daniel Jacobowitz
2003-08-18 15:10 ` Stephen Biggs
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 10:34 Michael Elizabeth Chastain
2003-08-18 8:10 Stephen Biggs
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=20030818125651.GA20363@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
--cc=xyzzy@hotpop.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).