git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Updated Kernel Hacker's guide to git

From
Willy Tarreau <w@1wt.eu>
Date
Dec 21, 2006, 05:44 UTC
Message-ID
<20061221054445.GL24090@1wt.eu>
In-Reply-To
<4589F9B1.2020405@garzik.org>
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

Previous: Jeff GarzikNext: Nigel Cunningham
Message 7 of 14 in “Updated Kernel Hacker's guide to git”
  1. Jeff GarzikDec 21, 2006
  2. Jay CliburnDec 21, 2006
  3. Martin LanghoffDec 21, 2006
  4. Junio C HamanoDec 21, 2006
  5. Linus TorvaldsDec 21, 2006
  6. Jeff GarzikDec 21, 2006
  7. Willy TarreauDec 21, 2006
  8. Nigel CunninghamDec 21, 2006
  9. Jeff GarzikDec 21, 2006
  10. Nigel CunninghamDec 21, 2006
  11. Francois RomieuDec 21, 2006
  12. Guennadi LiakhovetskiDec 21, 2006
  13. Jeff GarzikDec 21, 2006
  14. Jesper JuhlDec 22, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.