From: "David S. Miller" <davem@davemloft.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@oss.sgi.com
Subject: Re: [BK PATCHES] misc tg3 stuff
Date: Tue, 26 Oct 2004 11:55:55 -0700 [thread overview]
Message-ID: <20041026115555.390fcbbb.davem@davemloft.net> (raw)
In-Reply-To: <20041026165955.GA27136@havoc.gtf.org>
On Tue, 26 Oct 2004 12:59:55 -0400
Jeff Garzik <jgarzik@pobox.com> wrote:
> Please do a
>
> bk pull bk://kernel.bkbits.net/jgarzik/tg3-2.6
>
> This will update the following files:
>
> drivers/net/tg3.c | 22 +++++++++++-----------
> 1 files changed, 11 insertions(+), 11 deletions(-)
Your attached patch was full of e100 stuff and many
other totally unrelated changes, there were even crypto
layer diffs in there as well :-)
When you do range diffs with bitkeeper you have to
be really careful.
next parent reply other threads:[~2004-10-26 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041026165955.GA27136@havoc.gtf.org>
2004-10-26 18:55 ` David S. Miller [this message]
2004-10-26 19:15 ` [BK PATCHES] misc tg3 stuff Jeff Garzik
2004-10-26 19:33 ` David S. Miller
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=20041026115555.390fcbbb.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--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).