All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: David Dillow <dave@thedillows.org>
Cc: Netdev <netdev@oss.sgi.com>
Subject: Re: [PATCH 2.6] typhoon: fix PCI enable, add port IO option
Date: Fri, 07 Jan 2005 02:23:54 -0500	[thread overview]
Message-ID: <41DE390A.2050002@pobox.com> (raw)
In-Reply-To: <1105079709.6202.4.camel@ori.thedillows.org>

David Dillow wrote:
> On Thu, 2005-01-06 at 22:47 -0500, Jeff Garzik wrote:
> 
>>David Dillow wrote:
>>
>>>Jeff, please do a
>>>
>>>	bk pull http://typhoon.bkbits.net/typhoon-2.6
>>
>>Unfortunately, I can't pull this since it is not based on vanilla 
>>upstream 2.6.x.
> 
> 
> Heh, I based it off netdev-2.6 at the time, because, IIRC, there were
> changes in it that hadn't been pushed to Linus yet, and hadn't come
> through me to be picked up in my tree. (There may be a way for me to do
> it, I didn't try very hard.)

it's a natural guess to base it off of netdev-2.6, but that's mainly for 
people who send patches.  For BitKeeper, it's better to base it off a 
vanilla linux-2.6 tree.


>>Can you please re-create your typhoon repository, based only on Linus's 
>>2.6.x?
> 
> 
> Sure thing, it is there now. Content hasn't changed from the broken-out
> patches I sent earlier, but I broke the file deltas into changesets of
> their own.

thanks, pulled.

	Jeff

      reply	other threads:[~2005-01-07  7:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27  6:01 [PATCH 2.6] typhoon: fix PCI enable, add port IO option David Dillow
2005-01-07  3:47 ` Jeff Garzik
2005-01-07  6:35   ` David Dillow
2005-01-07  7:23     ` Jeff Garzik [this message]

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=41DE390A.2050002@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=dave@thedillows.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.