From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: [CVS note] New directory gdb/regformats/
Date: Sun, 03 Feb 2002 22:44:00 -0000 [thread overview]
Message-ID: <20020204014432.A23870@nevyn.them.org> (raw)
Andrew pointed out that anyone who doesn't do CVS updates with -d (get new
directories) is going to lose when I add rules to use the new regformats
directory. So, if you've got a checkout and do not automatically get new
directories, you may want to go into src/gdb/ and issue a
'cvs update -d regformats' in order to get it.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-02-04 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 22:44 Daniel Jacobowitz [this message]
2002-02-04 2:07 ` Richard Earnshaw
2002-02-04 16:01 ` Andrew Cagney
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=20020204014432.A23870@nevyn.them.org \
--to=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