linux-kernel - Re: [git pull] core fixes

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080818062218.GA1755@elte.hu>
Date:	Mon, 18 Aug 2008 08:22:18 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [git pull] core fixes

* Nick Piggin <nickpiggin@...oo.com.au> wrote:

> You didn't at all point to any *upsides* of your merging in this way, 
> so I assume there are none?

ah, i think i see where the confusion comes from. I assumed you knew 
that by the time your corrected patch arrived i already sent my pull 
request to Linus [having tested it and having found no immediate 
problems with it] and Linus already merged it?

So i did a delta patch and sent a second pull request, with a second 
branch. No puppies got hurt in the process as the two commits are close 
to each other and werent in fact pushed out by Linus separately.

Obviously you are right in the general case and we try to avoid 
splitting up fixes into two parts when possible.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/