From: Fedin Pavel <p.fedin@samsung.com>
To: 'Keith Seitz' <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: RE: Build problem - missing files ???
Date: Wed, 29 May 2013 10:31:00 -0000 [thread overview]
Message-ID: <001d01ce5c57$9f606d50$de2147f0$%fedin@samsung.com> (raw)
In-Reply-To: <51A4EC89.5060302@redhat.com>
Hello!
> If you are using CVS, make sure you have src/gdb/system-gdbinit. The "-
> d" option to "cvs update" might be necessary to grab this new directory.
> [FWIW, I regularly go into src/gdb and do cvs update -d to grab any new
> directories.]
Ops, thanks. I forgot that cvs needs a separate option for this...
Nobody except you uses cvs nowadays...
Kind regards.
prev parent reply other threads:[~2013-05-29 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 7:34 Fedin Pavel
2013-05-28 17:42 ` Keith Seitz
2013-05-29 10:31 ` Fedin Pavel [this message]
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='001d01ce5c57$9f606d50$de2147f0$%fedin@samsung.com' \
--to=p.fedin@samsung.com \
--cc=insight@sourceware.org \
--cc=keiths@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).