From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Question about "cvs update"
Date: Mon, 11 Oct 2010 07:56:00 -0000 [thread overview]
Message-ID: <20101011075555.GA30231@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <AANLkTikd5HiiO-joxSuJLMAhRzTbNiNUyDJj0HHaqhEh@mail.gmail.com>
On Mon, 11 Oct 2010 09:49:56 +0200, Hui Zhu wrote:
> Could someone tell me how to update the all src directory and do not
> co the files of other softwares.
Yes, one should not use -d for the sourceware tree.
To handle the cases of new directories I do completely new checkouts nightly.
As I use CVS only for check-ins (and GIT for real work with the tree) it has
no problems.
`cvs checkout' into the existing tree should update it, possibly with the
right directories tracking. But I was unable to set it up for sourceware.
Regards,
Jan
next prev parent reply other threads:[~2010-10-11 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 7:50 Hui Zhu
2010-10-11 7:56 ` Jan Kratochvil [this message]
2010-10-11 8:10 ` Hui Zhu
2010-10-11 15:25 ` Christopher Faylor
2010-10-11 18:59 ` Steffen DETTMER
2010-10-11 15:32 ` Daniel Jacobowitz
2010-10-11 16:28 ` Dave Korn
2010-10-11 16:43 ` Pedro Alves
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=20101011075555.GA30231@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=teawater@gmail.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