From: Jeff Garzik <jgarzik@pobox.com>
To: Andy Isaacson <adi@hexapodia.org>
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 21:31:03 -0500 [thread overview]
Message-ID: <41F9A3E7.5060607@pobox.com> (raw)
In-Reply-To: <20050128021530.GB19150@hexapodia.org>
Andy Isaacson wrote:
> 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`
Well, by "re-clone" I mean recreate. It's probably better to do what I
do, clone the latest linux-2.5 repo and the pull netdev-2.6 into that.
Far less messy than 'bk undo'.
Jeff
next prev parent reply other threads:[~2005-01-28 2:31 UTC|newest]
Thread overview: 26+ 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
2005-01-28 2:31 ` Jeff Garzik [this message]
-- 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-16 1:00 Jeff Garzik
2004-10-20 17:48 ` Olaf Hering
2004-10-20 22:33 ` Jeff Garzik
2004-10-01 4:59 Jeff Garzik
2004-09-20 19:48 Jeff Garzik
2004-09-20 20:14 ` Arkadiusz Miskiewicz
2004-09-20 20:31 ` Jeff Garzik
2004-09-20 20:38 ` Arkadiusz Miskiewicz
2004-08-29 1:00 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=41F9A3E7.5060607@pobox.com \
--to=jgarzik@pobox.com \
--cc=adi@hexapodia.org \
--cc=akpm@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.