From: Jeff Garzik <jeff@garzik.org>
To: NetDev <netdev@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: netdev tree status
Date: Fri, 18 Jul 2008 19:26:58 -0400 [thread overview]
Message-ID: <488126C2.2010208@garzik.org> (raw)
Just to let folks know, I was holding on to patches received, until
DaveM got net-2.6 and net-next upstream and sorted.
Since that update has now happened, patches should start flowing from my
mbox queue into my git queue (and on to DaveM) again.
It will be a few days to get things fully "unclogged" however :)
Jeff
reply other threads:[~2008-07-18 23:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=488126C2.2010208@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.