* Re: pull-request: mac80211 2014-12-18
[not found] <1418911822.6134.13.camel@sipsolutions.net>
@ 2014-12-18 20:35 ` David Miller
2014-12-18 20:54 ` Johannes Berg
0 siblings, 1 reply; 3+ messages in thread
From: David Miller @ 2014-12-18 20:35 UTC (permalink / raw)
To: johannes; +Cc: linux-wireless, netdev
From: Johannes Berg <johannes@sipsolutions.net>
Date: Thu, 18 Dec 2014 15:10:22 +0100
> Also from me a first pull request - we have a number of really old
> issues that happened to crop up now with new work (or just more testing)
> in the right areas as well as some small bugs newly introduced in 3.19.
>
> Let me know if there are any problems.
Pulled, but:
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.
2) I want every pull request I get at least CC:'d to netdev.
> The following changes since commit 5fbea33740aeb948422d7b7e8aafbeac362264b2:
>
> r8169:update rtl8168g pcie ephy parameter (2014-12-11 21:38:52 -0500)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-davem-2014-12-18
>
> for you to fetch changes up to 28a9bc68124c319b2b3dc861e80828a8865fd1ba:
>
> mac80211: free management frame keys when removing station (2014-12-17 14:00:17 +0100)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pull-request: mac80211 2014-12-18
2014-12-18 20:35 ` pull-request: mac80211 2014-12-18 David Miller
@ 2014-12-18 20:54 ` Johannes Berg
2014-12-18 21:01 ` David Miller
0 siblings, 1 reply; 3+ messages in thread
From: Johannes Berg @ 2014-12-18 20:54 UTC (permalink / raw)
To: David Miller; +Cc: linux-wireless, netdev
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pull-request: mac80211 2014-12-18
2014-12-18 20:54 ` Johannes Berg
@ 2014-12-18 21:01 ` David Miller
0 siblings, 0 replies; 3+ messages in thread
From: David Miller @ 2014-12-18 21:01 UTC (permalink / raw)
To: johannes; +Cc: linux-wireless, netdev
From: Johannes Berg <johannes@sipsolutions.net>
Date: Thu, 18 Dec 2014 21:54:29 +0100
> 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?
Anything you do I guess is fine with me, but I'm going to edit the
content that ends up in the merge commit regardless.
>> 2) I want every pull request I get at least CC:'d to netdev.
>
> Ok, sure.
Thanks.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-12-18 21:13 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
2014-12-18 21:01 ` David Miller
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).