From: Stephen Biggs <xyzzy@hotpop.com>
To: GDB list <gdb@sources.redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>
Subject: Re: binutils+gdb CVS module
Date: Mon, 18 Aug 2003 14:51:00 -0000 [thread overview]
Message-ID: <1061218286.18235.102.camel@steve.softier.local> (raw)
In-Reply-To: <20030818125651.GA20363@nevyn.them.org>
On Mon, 2003-08-18 at 15:56, Daniel Jacobowitz wrote:
> 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.
>
I did a checkout like so:
$ cd ~/cvs
$ cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/src login
$ cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/src checkout
binutils+gdb
... so, if I have ~/cvs/src being the top of my binutils+gdb tree (with
NO mention anywhere of binutils+gdb in the tree, fitting what Michael
said), from the level above, if I understand you correctly?
This doesn't work.
$ cd ~/cvs
$ cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/src update -R -d -P
binutils+gdb
cvs server: Updating binutils+gdb
cvs server: cannot open directory /cvs/src/binutils+gdb: No such file or
directory
cvs server: skipping directory binutils+gdb
$
What did I do wrong?
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
>
next prev parent reply other threads:[~2003-08-18 14:51 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
2003-08-18 13:03 ` Bob Rossi
2003-08-18 14:51 ` Stephen Biggs [this message]
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=1061218286.18235.102.camel@steve.softier.local \
--to=xyzzy@hotpop.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.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).