From: Valdis.Kletnieks@vt.edu
To: paulmck@linux.vnet.ibm.com
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
David Howells <dhowells@redhat.com>,
torvalds@osdl.org, git@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Simplified GIT usage guide
Date: Tue, 23 Dec 2008 23:35:18 -0500 [thread overview]
Message-ID: <43952.1230093318@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 18 Dec 2008 17:27:23 PST." <20081219012723.GI6912@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
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... ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-12-24 4:36 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 18:28 David Howells
2008-12-12 18:53 ` Miklos Vajna
2008-12-12 18:57 ` Johannes Schindelin
2008-12-19 0:02 ` Paul E. McKenney
2008-12-19 0:28 ` Junio C Hamano
2008-12-19 1:27 ` Paul E. McKenney
2008-12-24 4:35 ` Valdis.Kletnieks [this message]
2008-12-19 2:38 ` Johannes Schindelin
2008-12-19 5:25 ` Paul E. McKenney
2008-12-12 19:02 ` David Howells
2008-12-12 19:09 ` Miklos Vajna
2008-12-13 1:12 ` David Howells
2008-12-13 3:34 ` Miklos Vajna
2008-12-12 19:12 ` David Howells
2008-12-12 19:24 ` Sverre Rabbelier
2008-12-12 19:40 ` Aidan Van Dyk
2008-12-13 23:05 ` Nick Andrew
2008-12-14 1:45 ` Ping Yin
2008-12-12 19:39 ` Jakub Narebski
2008-12-12 19:47 ` J. Bruce Fields
2008-12-13 1:03 ` J. Bruce Fields
2008-12-13 1:14 ` David Howells
2008-12-12 20:00 ` Jeff Garzik
2008-12-12 21:34 ` Chris Friesen
2008-12-13 5:59 ` Junio C Hamano
2008-12-13 23:12 ` Nick Andrew
2008-12-12 20:07 ` Nicolas Pitre
2008-12-13 0:30 ` David Howells
2008-12-13 1:04 ` David Howells
2008-12-13 1:16 ` Sverre Rabbelier
2008-12-19 6:33 ` Willy Tarreau
2008-12-13 1:22 ` Nicolas Pitre
2008-12-13 3:35 ` Junio C Hamano
2008-12-14 10:33 ` Matthieu Moy
2008-12-14 17:33 ` Marcin Slusarz
2008-12-19 0:47 ` C. Scott Ananian
2008-12-19 9:26 ` Michael J Gruber
2008-12-19 17:08 ` C. Scott Ananian
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=43952.1230093318@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=Johannes.Schindelin@gmx.de \
--cc=dhowells@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®