From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: mac80211 2014-12-18
Date: Thu, 18 Dec 2014 21:54:29 +0100 [thread overview]
Message-ID: <1418936069.10864.1.camel@sipsolutions.net> (raw)
In-Reply-To: <20141218.153520.221364366280641527.davem@davemloft.net>
On Thu, 2014-12-18 at 15:35 -0500, David Miller wrote:
> 1) Don't put things into a merge commit, I take the text from your
> pull request email and that becomes the merge commit contents.
> Put it in your pull request email.
Hmm, ok - not sure I fully understand. I don't think I created a merge
commit, so did you mean the tag? I thought a (signed) tag with contents
was now the preferred way to send pull requests, but I can also send a
signed email without a tag for you to merge a branch? Or would you
prefer a signed tag but empty (is that even possible?) with the text in
the email?
> 2) I want every pull request I get at least CC:'d to netdev.
Ok, sure.
Thanks,
johannes
next prev parent reply other threads:[~2014-12-18 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1418911822.6134.13.camel@sipsolutions.net>
2014-12-18 20:35 ` pull-request: mac80211 2014-12-18 David Miller
2014-12-18 20:54 ` Johannes Berg [this message]
2014-12-18 21:01 ` 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=1418936069.10864.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-wireless@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 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).