From: David Miller <davem@davemloft.net>
To: antonio@meshcoding.com
Cc: netdev@vger.kernel.org
Subject: Re: merge net into net-next ?
Date: Mon, 06 Jan 2014 17:39:30 -0500 (EST) [thread overview]
Message-ID: <20140106.173930.2110538472481497348.davem@davemloft.net> (raw)
In-Reply-To: <52C93D6D.7050101@meshcoding.com>
From: Antonio Quartulli <antonio@meshcoding.com>
Date: Sun, 05 Jan 2014 12:09:33 +0100
> Do you have any plan about merging net into net-next?
This is now done.
next prev parent reply other threads:[~2014-01-06 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 11:09 merge net into net-next ? Antonio Quartulli
2014-01-06 6:16 ` David Miller
2014-01-06 22:39 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-08 12:10 merge net into net-next? Johannes Berg
2017-06-08 12:14 ` Johannes Berg
2017-06-08 14:19 ` David Miller
2017-06-08 14:19 ` David 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=20140106.173930.2110538472481497348.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=antonio@meshcoding.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).