DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type:content-transfer-encoding;
        b=UoUuC9zCCYZ7K4xyEvelaE/RasIxNM4f/IhjyvOY2bR54vhGFfvVoOsgWtHYItO9MYgM/n9IsY+xjOBD1gI9ebYFmhrPRwMhTmYFvh1FZItxYyb8ydqkFRqklQjzpQHSdI03ifueH4xtuPQE/M3g5zGb/Kqbq/RDf/d2hTdWvbA=
Date: Thu, 9 Feb 2006 16:35:46 +0100
From: Diego Calleja <diegocg@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: jes@sgi.com, pj@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: git for dummies, anyone?
Message-Id: <20060209163546.493334f8.diegocg@gmail.com>
In-Reply-To: <43EB4F05.8090400@pobox.com>
References: <20060208070301.1162e8c3.pj@sgi.com>
	<yq0vevollx4.fsf@jaguar.mkp.net>
	<43EB4F05.8090400@pobox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1628
Lines: 41

El Thu, 09 Feb 2006 09:17:41 -0500,
Jeff Garzik <jgarzik@pobox.com> escribi?:


> Check out:
> http://linux.yyz.us/git-howto.html

That is a nice guide, but is oriented to developers, I think jes
was asking from a user POV (I've needed to google for such things
several times) ie how to switch to a given tag and return to master,
how to update the repository periodically, etc; no stuff about how to
manage patches. It may be nice to see such thing on your guide, something
like this:


- How to get a copy of linus'tree
  git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

- Update your copy:
  cd linux-2.6; git pull; git pull --tags

- How to go back to a certain snapshot
  git reset --hard v2.6.13 (ls .git/refs/tags to see all the tags). Not the
  cleanest method, I think. "git-checkout -f master" will return to the "head"
  of the repository. You can also pass commit-IDs to git-reset instead of tags?

- bisect search
  git reset --hard BrokenVersion
  git bisect start
  git bisect good v2.6.13-rc2
  
  Compile, test, and do "git bisect good" or "git bisect bad" until you find
  the culprit. If it doesn't compile or something you can do a "git bisect good/bad"
  "git bisect reset" resets the repository when you are done.
  http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
  explains it with more detail.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/