From: "J. Bruce Fields" <bfields@fieldses.org>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Simplified GIT usage guide
Date: Fri, 12 Dec 2008 20:03:28 -0500 [thread overview]
Message-ID: <20081213010328.GA23224@fieldses.org> (raw)
In-Reply-To: <20081212194703.GA17573@fieldses.org>
On Fri, Dec 12, 2008 at 02:47:03PM -0500, bfields wrote:
> On Fri, Dec 12, 2008 at 06:28:27PM +0000, David Howells wrote:
> > Add a guide to using GIT's simpler features.
> >
> > Signed-off-by: David Howells <dhowells@redhat.com>
>
> Just a couple random thoughts:
(Also: this patch applies to either the git or linux trees, and you sent
it to both mailing lists. Looks like you meant it for linux, but you
might want to clarify....)
--b.
>
> - The advantage of adding this to the kernel tree is that you
> can tailor it for a more specific audience (kernel developers
> and testers). A lot of this (e.g. the object-database
> discussion) seems to be generic introduction-to-git stuff.
> Is there some canonical external documentation you could refer
> to for that stuff, that would allow you to get more quickly to
> the more tailored information? If not, is there something you
> could improve to the point where you *would* be comfortable
> referring to it?
> - How much overlap is there with
> Documentation/development-process/7.AdvancedTopics? Should
> there be cross-references between the two?
>
> There's an awful lot of introductions to git out there now (and I've got
> my own share of the blame).
next prev parent reply other threads:[~2008-12-13 1:05 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 18:28 [PATCH] Simplified GIT usage guide 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
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 [this message]
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=20081213010328.GA23224@fieldses.org \
--to=bfields@fieldses.org \
--cc=dhowells@redhat.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).