From: David Miller <davem@davemloft.net>
To: donald.c.skidmore@intel.com
Cc: netdev@vger.kernel.org
Subject: Re: [net-next 00/10][pull-request] Intel Wired LAN Driver Updates
Date: Wed, 05 Jan 2011 11:41:06 -0800 (PST) [thread overview]
Message-ID: <20110105.114106.39178014.davem@davemloft.net> (raw)
In-Reply-To: <20110105175920.GB23050@gitlad.jf.intel.com>
From: Don Skidmore <donald.c.skidmore@intel.com>
Date: Wed, 5 Jan 2011 09:59:20 -0800
> The following series contains:
> - ixgbe flow director improvement patches
> - general e1000 cleanup
> - switches ixgbe to new vlan interface
>
> The following are changes since commit:
>
> commit 2316aa2aee254c126e688b53a3a105b82bc3f368
> Author: Greg Rose <gregory.v.rose@intel.com>
> ixgbevf: Add X540 VF device support to the ixgbevf driver
>
> and are available in the git repository at:
>
> master.kernel.org:/pub/scm/linux/kernel/git/jkirsher/net-next-2.6.git master
There's nothing there.
davem@sunset:~/src/GIT/net-next-2.6$ git pull master.kernel.org:/pub/scm/linux/kernel/git/jkirsher/net-next-2.6.git master
davem@master.kernel.org's password:
Permission denied, please try again.
davem@master.kernel.org's password:
>From master.kernel.org:/pub/scm/linux/kernel/git/jkirsher/net-next-2.6
* branch master -> FETCH_HEAD
Already up-to-date.
davem@sunset:~/src/GIT/net-next-2.6$
Also all of your patch emails went out with the actual SMTP
"From: " changed, so it looks as if the patch author actually
sent those patch emails.
That's not what it should look like, the top level From: should
be you, and at the top of the commit message body there should
be another "From: " line demarking the patch author.
parent reply other threads:[~2011-01-05 19:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20110105175920.GB23050@gitlad.jf.intel.com>]
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=20110105.114106.39178014.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=donald.c.skidmore@intel.com \
--cc=netdev@vger.kernel.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 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).