From: Bob Rossi <bob@brasko.net>
To: Doug Evans <dje@transmeta.com>
Cc: gdb@sources.redhat.com
Subject: Re: cvs update
Date: Thu, 07 Aug 2003 15:26:00 -0000 [thread overview]
Message-ID: <20030807152546.GA21305@white> (raw)
In-Reply-To: <16178.28322.667811.103790@casey.transmeta.com>
wooo, I didn't know you could do that. Thanks!
It seems like your saying there are many ways to do it. It also seems
like you are saying to *not* just update the gdb tree. I have to update
everything it depends on?
I am new at working with gdb, sorry for the low level questions.
Thanks,
Bob Rossi
On Thu, Aug 07, 2003 at 08:22:10AM -0700, Doug Evans wrote:
> Doug Evans writes:
> > Bob Rossi writes:
> > > If I do need to update several packages, is there a list? or should I
> > > just do it from the top level?
> >
> > Or, if you checked out both gdb and binutils, say with:
> >
> > bash$ cvs -d ':pserver:anoncvs@sources.redhat.com:/cvs/src' checkout gdb binutils
> >
> > then, again, update the same way:
> >
> > bash$ cvs -d ':pserver:anoncvs@sources.redhat.com:/cvs/src' checkout gdb binutils
>
> Sorry to follow-up my own message. I forgot something.
>
> You can see what modules are available to checkout with
>
> bash$ cvs -d ':pserver:anoncvs@sources.redhat.com:/cvs/src' checkout modules
>
> and browse file modules/modules.
>
> Note that there is a combined gdb+binutils module, thus you can do:
>
> bash$ cvs -d ':pserver:anoncvs@sources.redhat.com:/cvs/src' checkout gdb+bintuils
>
> Dunno how permanent the gdb+binutils module is.
next prev parent reply other threads:[~2003-08-07 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 11:32 Bob Rossi
2003-08-07 15:08 ` Doug Evans
2003-08-07 15:22 ` Doug Evans
2003-08-07 15:26 ` Bob Rossi [this message]
2003-08-07 16:08 ` Doug Evans
2003-08-07 15:36 ` David Carlton
2003-08-07 15:50 Michael Elizabeth Chastain
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=20030807152546.GA21305@white \
--to=bob@brasko.net \
--cc=dje@transmeta.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