From: Tom Tromey <tromey@redhat.com>
To: Joel Sherrill <joel.sherrill@OARcorp.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: cgen/bitset.h missing??
Date: Thu, 25 Mar 2010 20:23:00 -0000 [thread overview]
Message-ID: <m34ok4ducm.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4BABC55C.3060607@oarcorp.com> (Joel Sherrill's message of "Thu, 25 Mar 2010 15:19:40 -0500")
>>>>> "Joel" == Joel Sherrill <joel.sherrill@OARcorp.com> writes:
Joel> Ahh.. I usually don't to the -d on the gdb
Joel> checkout because it seems to add code
Joel> that wasn't there at the checkout.
Yeah .. actually, I never use "update" with gdb, because cvs won't
remember the modules I used at checkout time, and so that will pull in
all kinds of stuff from the src repository. Instead I just re-run the
original checkout command. This respects modules and is as efficient as
update anyway.
Tom
next prev parent reply other threads:[~2010-03-25 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 19:10 Joel Sherrill
2010-03-25 20:08 ` Tom Tromey
2010-03-25 20:19 ` Joel Sherrill
2010-03-25 20:23 ` Tom Tromey [this message]
2010-03-25 21:16 ` Christopher Faylor
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=m34ok4ducm.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=joel.sherrill@OARcorp.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