From: Jeff Garzik <jgarzik@pobox.com>
To: Auke Kok <sofar@foo-projects.org>
Cc: netdev@vger.kernel.org, auke-jan.h.kok@intel.com,
auke@foo-projects.org, akpm@osdl.org
Subject: Re: [RESEND] please pull from git://lost.foo-projects.org/~ahkok/git/netdev-2.6 upstream
Date: Wed, 05 Jul 2006 14:33:54 -0400 [thread overview]
Message-ID: <44AC0612.8000300@pobox.com> (raw)
In-Reply-To: <b89f3df8c8420144e0cbf36dd56daa6b@localhost>
Auke Kok wrote:
> Jeff,
>
> Since my pull request from thursday I haven't heard anything anymore, so I
> assume that the changes we made were sufficient.
>
> Needless to say that I would love to see ich8 support make it into 2.6.18rc,
> considering that the hardware already is out there and the code has been
> tested and validated extensively over the last period.
>
> I hope that can still be accomodated. In that light, please pull:
>
> git://lost.foo-projects.org/~ahkok/git/netdev-2.6 upstream
pulled, and updated for the conflict
prev parent reply other threads:[~2006-07-05 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 20:58 [RESEND] please pull from git://lost.foo-projects.org/~ahkok/git/netdev-2.6 upstream Auke Kok
2006-07-05 18:33 ` 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=44AC0612.8000300@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=auke-jan.h.kok@intel.com \
--cc=auke@foo-projects.org \
--cc=netdev@vger.kernel.org \
--cc=sofar@foo-projects.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 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.