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
| ||
|
Date: Tue, 12 Mar 2013 15:00:24 -0700 From: Junio C Hamano <gitster@...ox.com> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: "Theodore Ts'o" <tytso@....edu>, James Morris <jmorris@...ei.org>, Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Git Mailing List <git@...r.kernel.org> Subject: Re: linux-next: unneeded merge in the security tree Linus Torvalds <torvalds@...ux-foundation.org> writes: > That said, adding the signature from an upstream tag doesn't really > seem to be hugely useful. I'm not seeing much of an upside, in other > words. I'd *expect* that people would pick up upstream tags > regardless, no? Yes, their "git fetch" will auto-follow, but mergetag embedded in the commit objects will give the history auditable trail the same way as the merges you make your downstream. You of course could match out-of-line tags against back-merges and verify your merges with mergetags, but you do not have to. -- 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