From: "Mikael Magnusson" <mikachu@gmail.com>
To: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: [RFD] How to better document the "two and three dots" format
Date: Mon, 1 Sep 2008 14:49:12 +0200 [thread overview]
Message-ID: <237967ef0809010549n72629d47gfdf3c483f1a9e369@mail.gmail.com> (raw)
In-Reply-To: <4d8e3fd30809010543o1e1562c1s4466e191e782ddcc@mail.gmail.com>
2008/9/1 Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>:
> Hi all,
> I'm looking in the existing documentation about some example and
> clarification about
> the two and three dots formats applied to git diff.
>
> The git-diff.txt file includes the following:
>
> ---8<---
> Comparing branches::
> +
> ------------
> $ git diff topic master <1>
> $ git diff topic..master <2>
> $ git diff topic...master <3>
> ------------
> +
> <1> Changes between the tips of the topic and the master branches.
> <2> Same as above.
> <3> Changes that occurred on the master branch since when the topic
> branch was started off it.
> ---8<---
>
> I think <3> should be changed in something like:
> <3> Changes between the tips of the topic and the master branch that
> occurred since when the topic
> branch was started off it.
>
> What do you think?
Your proposed sentence is incorrect, the diff doesn't involve the tip
of topic at all. It shows the diff between the merge-base and the tip
of master. Ie, the combined diff of all the commits in the rev-list
range topic..master.
> I would like to add some graphical representation of <2> and <3> but
> I'm a bit loss
> with <3> (and I guess lot of newbies are not really understanding that point).
> Can anybody come up with some ASCII art?
>
> Thanks.
>
> Ciao,
--
Mikael Magnusson
next prev parent reply other threads:[~2008-09-01 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 12:43 [RFD] How to better document the "two and three dots" format Paolo Ciarrocchi
2008-09-01 12:49 ` Mikael Magnusson [this message]
2008-09-01 13:01 ` Daniël Gressmann
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=237967ef0809010549n72629d47gfdf3c483f1a9e369@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=git@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
/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).