lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20141218.160114.2087947503269562870.davem@davemloft.net>
Date:	Thu, 18 Dec 2014 16:01:14 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	johannes@...solutions.net
Cc:	linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: pull-request: mac80211 2014-12-18

From: Johannes Berg <johannes@...solutions.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ