From ncunningham@crca.org.au  Wed Jul 16 23:45:22 2008
Return-Path: <ncunningham@crca.org.au>
X-Original-To: tuxonice-devel@lists.tuxonice.net
Delivered-To: tuxonice-devel@crca.org.au
X-Bogosity: Ham, spamicity=0.000000
Received: from [10.1.1.5] (home.nigel.suspend2.net [203.171.70.205])
	by crca.org.au (Postfix) with ESMTP id 09890138004;
	Wed, 16 Jul 2008 23:45:20 +0000 (UTC)
From: Nigel Cunningham <ncunningham@crca.org.au>
To: Kenneth Crudup <kenny@panix.com>
In-Reply-To: <Pine.LNX.4.64.0807161608550.14425@hp9800.localdomain>
References: <Pine.LNX.4.64.0807161334510.10419@hp9800.localdomain>
	<1216237468.9989.7.camel@nigel-laptop>
	<Pine.LNX.4.64.0807161608550.14425@hp9800.localdomain>
Content-Type: text/plain
Organization: Christian Reformed Churches of Australia
Date: Thu, 17 Jul 2008 09:45:19 +1000
Message-Id: <1216251919.9989.42.camel@nigel-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.2 
Content-Transfer-Encoding: 7bit
Cc: tuxonice-devel@lists.tuxonice.net
Subject: Re: [TuxOnIce-devel] How do you "back out" a "git pull"?
X-BeenThere: tuxonice-devel@lists.tuxonice.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TuxOnIce Development Discussion <tuxonice-devel.lists.tuxonice.net>
List-Unsubscribe: <http://lists.tuxonice.net/mailman/listinfo/tuxonice-devel>, 
	<mailto:tuxonice-devel-request@lists.tuxonice.net?subject=unsubscribe>
List-Archive: <http://lists.tuxonice.net/pipermail/tuxonice-devel>
List-Post: <mailto:tuxonice-devel@lists.tuxonice.net>
List-Help: <mailto:tuxonice-devel-request@lists.tuxonice.net?subject=help>
List-Subscribe: <http://lists.tuxonice.net/mailman/listinfo/tuxonice-devel>,
	<mailto:tuxonice-devel-request@lists.tuxonice.net?subject=subscribe>
X-List-Received-Date: Wed, 16 Jul 2008 23:45:22 -0000

Hi.

On Wed, 2008-07-16 at 16:11 -0700, Kenneth Crudup wrote:
> On Thu, 17 Jul 2008, Nigel Cunningham wrote:
> 
> > Finding the commit you're after could be done by:
> > - using gitk and noting the (long) sha id
> > - making a (temporary) branch before pulling
> >     and then doing git checkout -f {branchname}
> > - if the reference is tagged, using the tag (eg v2.6.26)
> > You could then git seek to the reference.
> 
> > Hope that helps!
> 
> Heh- it "helps" me realize I need to get me to a GIT ref page ASAP! I got
> very little of that, conceptually.
> 
> I dunno why Linus has such a hard-on for GIT [1]; I've used a bunch of
> CM tools and just not getting what's so great about it above all others.
> 
> 	-Kenny
> 
> [1] - but I'm assuming his authorship has something to do with it

It's like Linux in general - a steep learning curve, but once you get
used to it you won't want to look back. I'm still on the learning curve
- by no means an expert - but I like it better than bitkeeper and way
better than svn, cvs, etc. Then again, I tend to wrap the commands in
nice little scripts so that I don't have to remember them all the
time :)

Nigel


