[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <43952.1230093318@turing-police.cc.vt.edu>
Date: Tue, 23 Dec 2008 23:35:18 -0500
From: Valdis.Kletnieks@...edu
To: paulmck@...ux.vnet.ibm.com
Cc: Junio C Hamano <gitster@...ox.com>,
Johannes Schindelin <Johannes.Schindelin@....de>,
David Howells <dhowells@...hat.com>, torvalds@...l.org,
git@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Simplified GIT usage guide
On Thu, 18 Dec 2008 17:27:23 PST, "Paul E. McKenney" said:
> I would be OK with it being in linux-2.6.git rather than git.git,
> if that helps. Certainly there seems to be room for a description
> of how to use git within the Linux community.
What might help a lot of people (me, for one) would be a cookbook listing
how to do things that those of us on the fringe might want to do. For example:
"type this to pull Linus's tree, and this to bisect it" (I already know how
to do this one, actually)
"type this to pull a linux-next tree, and this to bisect it" (Last time I tried,
the pull went OK, but I couldn't figure out how to give 'git bisect' a
start/end commit that it was happy with).
"'git log foo/bar/baz.c' is your friend if you're chasing a recently added
bug/regression in baz.c"
Hmm... it occurs to me that my only actual use for git is to find a commit
ID so when I whinge to a developer, we're on the same page... ;)
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists