| 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
| ||
|
Message-ID: <1299878274.2814.8.camel@bwh-desktop> Date: Fri, 11 Mar 2011 21:17:54 +0000 From: Ben Hutchings <bhutchings@...arflare.com> To: David Miller <davem@...emloft.net> Cc: bfields@...ldses.org, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [GIT] Networking On Fri, 2011-03-11 at 13:01 -0800, David Miller wrote: > From: "J. Bruce Fields" <bfields@...ldses.org> > Date: Fri, 11 Mar 2011 15:48:23 -0500 > > > As with the above, it'd make the history a little more self-documenting. > > Once there is even one single commit after the buggy one, this is > simply impossible since the hashes of subsequent commits depend upon > the precise contents of the original one. I think Bruce is suggesting that the fix is committed on a branch from the broken commit, then merged into whatever branches need it. I'm not sure how much that helps, though. The merge could then involve forward- porting (as opposed to the current situation where fixes are cherry- picked and possibly back-ported). Ben. -- Ben Hutchings, Senior Software Engineer, Solarflare Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked. -- 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/
Powered by blists - more mailing lists