All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: [howto] Kernel hacker's guide to git, updated
Date: Fri, 30 Sep 2005 20:17:25 -0400	[thread overview]
Message-ID: <433DD595.4070508@pobox.com> (raw)
In-Reply-To: <200509301813.j8UIDXr5015488@laptop11.inf.utfsm.cl>

Horst von Brand wrote:
> 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




  reply	other threads:[~2005-10-01  0:17 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 11:03 [howto] Kernel hacker's guide to git, updated Jeff Garzik
2005-09-29 15:18 ` David Leimbach
2005-09-29 16:03   ` Alberto Patino
2005-09-29 16:13     ` David Leimbach
2005-09-29 19:08 ` Oliver Neukum
2005-09-29 19:34   ` Jon Loeliger
2005-09-29 19:38     ` Oliver Neukum
2005-09-30  7:37       ` Junio C Hamano
2005-09-30  8:36         ` Oliver Neukum
2005-09-30 16:39         ` Linus Torvalds
2005-09-29 20:02 ` Dave Jones
2005-09-29 20:07   ` Anton Altaparmakov
2005-09-29 20:11     ` Dave Jones
2005-09-29 21:14       ` Linus Torvalds
2005-09-29 21:26         ` Linus Torvalds
2005-09-29 21:33           ` Dave Jones
2005-09-29 21:55             ` Linus Torvalds
2005-09-29 22:12               ` Anton Altaparmakov
2005-09-29 22:25                 ` Linus Torvalds
2005-09-29 22:32                   ` Anton Altaparmakov
2005-09-29 23:19                 ` Junio C Hamano
2005-09-30 12:22                   ` Johannes Schindelin
2005-09-29 23:17               ` Horst von Brand
2005-09-30  0:47                 ` Linus Torvalds
2005-09-30  1:54                   ` Junio C Hamano
2005-09-30  2:36                     ` Linus Torvalds
2005-10-01  0:10                   ` Linus Torvalds
2005-10-01  1:58                     ` Horst von Brand
2005-10-03  1:03                       ` Linus Torvalds
2005-09-29 21:33           ` Elfyn McBratney
2005-09-29 21:35           ` Linus Torvalds
2005-09-29 21:40             ` Dave Jones
2005-09-29 20:15   ` Jeff Garzik
2005-09-29 21:04     ` Junio C Hamano
2005-09-30 11:15       ` Jeff Garzik
2005-09-30 11:55         ` Junio C Hamano
2005-09-30 14:11           ` Jeff Garzik
2005-10-02  8:47             ` Junio C Hamano
2005-09-30 18:14           ` Linus Torvalds
2005-10-01  7:36             ` Junio C Hamano
2005-09-30 12:02         ` Oliver Neukum
2005-09-30 13:58           ` Jeff Garzik
2005-09-30 15:10             ` Alberto Patino
2005-09-30 12:07         ` Erik Mouw
2005-09-30 14:08           ` Jeff Garzik
2005-09-30 18:13         ` Horst von Brand
2005-10-01  0:17           ` Jeff Garzik [this message]
2005-09-30 22:52         ` Francois Romieu
2005-09-29 21:23     ` Chuck Lever
2005-10-04 11:44 ` Rolf Offermanns

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=433DD595.4070508@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vonbrand@inf.utfsm.cl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.