From: David Kastrup <dak@gnu.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Terminology question about remote branches.
Date: Sun, 05 Aug 2007 11:44:12 +0200 [thread overview]
Message-ID: <85fy2yb9jn.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20070805093232.GC12507@coredump.intra.peff.net> (Jeff King's message of "Sun\, 5 Aug 2007 05\:32\:32 -0400")
Jeff King <peff@peff.net> writes:
> On Sun, Aug 05, 2007 at 11:29:12AM +0200, David Kastrup wrote:
>
>> The main question is why I can't find this explained in this manner in
>> the documentation. Are you going to put it in yourself, or should I
>> attempt doing it?
>
> I guess because nobody complained it wasn't there before. :) Some of the
> information is a bit under-the-hood for most end-users, but obviously in
> your case the lack of information was creating confusion about the
> terms.
>
> Why don't you take a stab at updating the documentation (since you are
> the one who knows which parts were confusing you),
Well, one problem is that there simply _is_ no part of the
documentation where such an explanation would have a place. It does
not fit in the man pages of git-branch/git-commit, it has some passing
relation to the repository layout explanation (even though the latter
should not be something that the user has to read and understand for
basic operation), it may have some place in the user manual, but may
be a bit technical/long for that. Or one places it into another
isolated file and hopes that a user will stumble across it when in
need of the information.
Hm. Probably the usermanual is the best option in the current scheme
of things.
> and I will be more than happy to help with making sure the changes
> are accurate.
Thanks.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-08-05 9:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 10:55 Terminology question about remote branches David Kastrup
2007-08-04 12:02 ` Jeff King
2007-08-04 12:36 ` David Kastrup
2007-08-04 13:07 ` Lars Hjemli
2007-08-04 13:38 ` David Kastrup
2007-08-04 14:03 ` Lars Hjemli
2007-08-04 14:11 ` David Kastrup
2007-08-04 14:25 ` David Kastrup
2007-08-04 14:35 ` Lars Hjemli
2007-08-04 15:09 ` David Kastrup
2007-08-04 15:48 ` Lars Hjemli
2007-08-05 9:24 ` Jeff King
2007-08-04 14:50 ` Julian Phillips
2007-08-04 17:00 ` David Kastrup
2007-08-04 17:19 ` Julian Phillips
2007-08-04 18:00 ` David Kastrup
2007-08-04 22:56 ` Theodore Tso
2007-08-05 7:06 ` David Kastrup
2007-08-05 9:21 ` Jeff King
2007-08-05 9:29 ` David Kastrup
2007-08-05 9:32 ` Jeff King
2007-08-05 9:44 ` David Kastrup [this message]
2007-08-05 9:46 ` Jeff King
2007-08-04 12:14 ` Jakub Narebski
2007-08-04 13:29 ` Sean
2007-08-04 14:01 ` David Kastrup
2007-08-04 14:48 ` Sean
2007-08-04 15:22 ` David Kastrup
2007-08-05 10:10 ` Jeff King
2007-08-05 10:05 ` Jeff King
2007-08-05 10:56 ` Steffen Prohaska
2007-08-05 11:02 ` Jeff King
2007-08-05 11:38 ` David Kastrup
2007-08-05 11:52 ` Jeff King
2007-08-05 12:12 ` David Kastrup
2007-08-05 12:14 ` Jeff King
2007-08-05 15:48 ` Theodore Tso
2007-08-05 16:23 ` David Kastrup
2007-08-05 16:27 ` Randal L. Schwartz
2007-08-05 16:40 ` Sean
2007-08-05 16:45 ` Jeff King
2007-08-05 7:31 ` Junio C Hamano
2007-08-05 10:07 ` Steffen Prohaska
2007-08-05 14:23 ` Julian Phillips
2007-08-05 15:09 ` David Kastrup
2007-08-05 15:24 ` Julian Phillips
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=85fy2yb9jn.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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