From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: linux-kernel@vger.kernel.org
Subject: Re: missing files in bk trees?
Date: Wed, 24 Mar 2004 03:48:54 -0500 [thread overview]
Message-ID: <m3ptb2eikp.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <20040324043521.GA28169@thunk.org> (Theodore Ts'o's message of "Tue, 23 Mar 2004 23:35:22 -0500")
>>>>> "Josh" == Joshua Kwan <joshk@triplehelix.org> writes:
>>>>> "Ted" == Theodore Ts'o <tytso@mit.edu> writes:
Josh> you need to do 'bk -r get' in the root of your checkout
Ted> Better to do a "bk -r get -S", actually. That way files
Ted> that are already checked out won't be created a second time.
And even better, add a -U to skip the deleted files and others
under the BitKeeper dir:
bk -r -U get -S
-JimC
next prev parent reply other threads:[~2004-03-24 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 2:41 missing files in bk trees? ameer armaly
2004-03-24 2:50 ` Joshua Kwan
2004-03-24 4:35 ` Theodore Ts'o
2004-03-24 8:48 ` James H. Cloos Jr. [this message]
2004-03-24 9:12 ` Gabriel Paubert
2004-03-24 20:01 ` Andy Isaacson
2004-03-24 21:02 ` missing files in bk tree ameer armaly
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=m3ptb2eikp.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=linux-kernel@vger.kernel.org \
/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