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

Re: [howto] Kernel hacker's guide to git, updated

From
JGJeff Garzik <jgarzik@pobox.com>
Date
Oct 1, 2005, 00:17 UTC
Message-ID
<433DD595.4070508@pobox.com>
In-Reply-To
<200509301813.j8UIDXr5015488@laptop11.inf.utfsm.cl>
Horst von Brand wrote:
Show 11 quoted lines
> Jeff Garzik <jgarzik@pobox.com> wrote:
> 
>>Thanks for all the comments.  I just updated the KHGtG with the
>>feedback I received.  Go to
>>
>>	http://linux.yyz.us/git-howto.html
>>
>>and click reload.  Continued criticism^H^H^Hcomments welcome!
> 
> 
> - To know the current branch, "git branch" is enough (the one '*'-ed)
Click reload, this is already mentioned.
> - rsync(1) a repository is dangerous, it might catch it in the middle of
>   a update and give you an incomplete/messed up copy. Repeat rsync until no
>   change, perhaps?

Usually that's just unlucky. I have caught kernel.org in the middle of a sync once, maybe twice.

> - I understand "git checkout -f" blows away any local changes, no questions
>   asked. Not very nice to suggest that to a newbie...

I constantly run into problems if I -do not- use the "-f" flag. I habitually use it at all times, now.

Thanks,
	Jeff
Previous: Horst von Brand
Message 3 of 3 in “Re: Updated git HOWTO for kernel hackers”
  1. Horst von BrandJun 23, 2005
  2. Horst von BrandSep 30, 2005
  3. Jeff GarzikOct 1, 2005

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.