From: Nicolas Pitre <nico@cam.org>
Date: Mon, 09 Feb 2009 20:42:07 GMT
Subject: Re: git ready: daily git tips
Message-ID: <alpine.LFD.2.00.0902091524520.30940@xanadu.home>
In-Reply-To: <1234131508141-2294642.post@n2.nabble.com>

On Sun, 8 Feb 2009, Nick Quaranto wrote:

> 
> I started this blog just around a month ago on a quest to learn more about
> git on a daily basis and to show others how awesome it is. If you have any
> suggestions on what content to cover or how things should be done
> differently, I would greatly appreciate it. Thanks!
> 
> http://gitready.com

Well done.

One topic that IMHO you fail to cover, and which is being neglected 
almost everywhere else too, is the reflog.

The reflog is really your safety net when working with git.  It records 
everything you do. So even if you screw up a rebase, perform the wrong 
merge, or any other kind of undesired operation, then you may always go 
back to a previous state.  Either you use -g with 'git log' to see all 
those recorded states, or even 'git reflog' without any argument to get 
a condensed list for HEAD.

The <branch>@{<spec>} notation can be used anywhere a ref is normally 
required.  The special branch "HEAD" shows every state the HEAD pointer 
went through, including branch switches.  The <branch< part can be left 
out to mean "currently checked-out branch".

One thing that I use all the time after a 'git pull' is 'git log @{1}..' 
where "@{1}" means the first previous tip of the current branch, so 
effectively showing me the log of what the pull brought in my branch.


Nicolas