| 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: <1374686174.3356.135.camel@gandalf.local.home> Date: Wed, 24 Jul 2013 13:16:14 -0400 From: Steven Rostedt <rostedt@...dmis.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: "gregkh@...uxfoundation.org >> Kroah-Hartman, Greg" <gregkh@...uxfoundation.org>, Shuah Khan <shuah.kh@...sung.com>, Shuah Khan <shuahkhan@...il.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, "stable@...r.kernel.org" <stable@...r.kernel.org> Subject: Re: [ 000/103] 3.10.3-stable review On Wed, 2013-07-24 at 10:04 -0700, Linus Torvalds wrote: > The alternative workflow is to tell git to track the new files added > by the patch. So if you use "git apply --index", git will not just > apply the patch, it will also add the result to the index - so you > could commit it with a single "git commit", and you can see the diff - > including new files - with "git diff --cached". And then "git reset > --hard" will also undo the new files. I don't know why "git apply" doesn't do it by default. Why would you want to apply a patch without having git track new files? This burnt me a few times when working with the -rt patch until I found to use "--index" always. -- Steve -- 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