linux-kernel - Re: HTC Dream aka. t-mobile g1 support

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 11 Jun 2009 14:37:36 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Tony Lindgren <tony@...mide.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	David Miller <davem@...emloft.net>, swetland@...gle.com,
	pavel@....cz, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk, san@...roid.com,
	rlove@...gle.com
Subject: Re: HTC Dream aka. t-mobile g1 support

On Thu, Jun 11, 2009 at 06:21:35AM -0700, Tony Lindgren wrote:
> We've done this for two merge windows now for omap patches where the
> patches have been posted to linux-arm-kernel, then they go into the
> for-next tree, and then Russell merges them in.
> 
> It has worked OK, although Russell had some comments about having hard
> time keeping track on what he had reviewed already.

Yes, as I understand it, there was a closed room discussion between
several folk about how you'd handle sending your next round of patches
to me.

What you apparantly decided (and I'm saying this from how it appeared
on the receiving end and sort-of had it confirmed by Kevin in conference)
is that you'd send a patch set for me to review, I'd review it, and then
you'd merge it within your git tree into a branch for me.  You'd then do
the same thing with the next patch set, and so forth.

Eventually, near the merge window, you sent a pull request for the
entire lot, by which time I looked at the list of changes and wondered
whether that encompassed everything you'd asked me to review, or whether
it contained extra stuff, or whether it was for something quite different,
or what.

So by separating the review from the merge by weeks or even months, it
created additional problems.
--
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/