| 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: Thu, 21 Dec 2006 06:44:45 +0100 From: Willy Tarreau <w@....eu> To: Jeff Garzik <jeff@...zik.org> Cc: Linux Kernel <linux-kernel@...r.kernel.org>, Git Mailing List <git@...r.kernel.org> Subject: Re: Updated Kernel Hacker's guide to git Hi Jeff ! On Wed, Dec 20, 2006 at 10:04:17PM -0500, Jeff Garzik wrote: > I refreshed my git intro/cookbook for kernel hackers, at > http://linux.yyz.us/git-howto.html Thanks for this update, it was my most useful source of inspiration when I started with git. > This describes most of the commands I use in day-to-day kernel hacking. > Let me know if there are glaring errors or missing key commands. I very often use "git-format-patch -k -m" to produce individual patches that I delay, merge in other branches, or even in other trees with "git-am -k -3". I believe it was Davem who suggested this a while ago, and I agree it's very convenient to maintain a patch collection (and sometimes to clean them up). Also, I think that for beginners, you have not insisted enough on the fact that they should not modify the master branch, but that they should immediately create their own branch before any local changes. I got caught by this when I started, and had trouble playing with the origin branch to try to fix my mistakes. Overall it's a good tutorial anyway. Cheers, Willy - 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