From: David Howells <dhowells@redhat.com>
To: davem@davemloft.net
Cc: dhowells@redhat.com, netdev@vger.kernel.org,
linux-afs@lists.infradead.org,
Tim Smith <tim@electronghost.co.uk>,
Alexey Khoroshilov <khoroshilov@ispras.ru>,
linux-kernel@vger.kernel.org
Subject: Do you prefer git pulls or patches posting for networking stuff?
Date: Tue, 28 Jan 2014 20:11:17 +0000 [thread overview]
Message-ID: <10615.1390939877@warthog.procyon.org.uk> (raw)
In-Reply-To: <8672.1390928856@warthog.procyon.org.uk>
Hi Dave,
Do you prefer git pulls or patches posting for networking stuff?
David
next prev parent reply other threads:[~2014-01-28 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 17:07 [GIT PULL] AF_RXRPC fixes David Howells
2014-01-28 20:11 ` David Howells [this message]
2014-01-28 20:16 ` Do you prefer git pulls or patches posting for networking stuff? David Miller
2014-01-29 2:05 ` [GIT PULL] AF_RXRPC fixes 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=10615.1390939877@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=khoroshilov@ispras.ru \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tim@electronghost.co.uk \
/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).