From: Andy Isaacson <adi@hexapodia.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Netdev <netdev@oss.sgi.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Jouni Malinen <jkmaline@cc.hut.fi>
Subject: Re: netdev-2.6 queue updated
Date: Thu, 27 Jan 2005 18:15:30 -0800 [thread overview]
Message-ID: <20050128021530.GB19150@hexapodia.org> (raw)
In-Reply-To: <41F980A0.8020905@pobox.com>
On Thu, Jan 27, 2005 at 07:00:32PM -0500, Jeff Garzik wrote:
> The attached changelog describes what I just pushed out to BitKeeper
> (and what should be appearing in the next -mm release from Andrew).
>
> Note to BK users: please re-clone netdev-2.6, don't just 'bk pull'.
It's much more efficient to do
% bk undo -a`bk repogca`
(which deletes everything in the local repo that's not in the parent)
rather than pulling the entire repo over the wire again. [1]
You can check what would be deleted by this command with "bk changes -L"
similar to how you can "bk changes -R" to figure out what would be
pulled.
[1] Well, actually, it isn't *quite* that simple; in certain cases,
repogca will delete more than it needs to. But it's still more
efficient than a re-pull.
-andy
next prev parent reply other threads:[~2005-01-28 2:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 0:00 netdev-2.6 queue updated Jeff Garzik
2005-01-28 2:15 ` Andy Isaacson [this message]
2005-01-28 2:31 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 6:57 Jeff Garzik
2005-03-23 3:32 Jeff Garzik
2005-03-23 7:55 ` bert hubert
2005-03-23 8:57 ` Jeff Garzik
2005-03-10 5:37 Jeff Garzik
2005-03-03 7:31 Jeff Garzik
2005-03-03 20:20 ` Daniel Drake
2005-03-04 5:11 ` Jeff Garzik
2005-02-13 20:38 Jeff Garzik
2005-01-07 11:34 Jeff Garzik
2005-01-07 19:04 ` Francois Romieu
2005-01-07 19:11 ` Jeff Garzik
2004-11-05 10:02 Jeff Garzik
2004-10-01 4:59 Jeff Garzik
2004-09-20 19:48 Jeff Garzik
2004-07-27 19:05 Jeff Garzik
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=20050128021530.GB19150@hexapodia.org \
--to=adi@hexapodia.org \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=jkmaline@cc.hut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 NNTP newsgroup(s).