From: Junio C Hamano <gitster@pobox.com>
To: Adam Spiers <git@adamspiers.org>
Cc: git mailing list <git@vger.kernel.org>
Subject: Re: questions / suggestions about history simplification
Date: Thu, 19 Dec 2013 12:37:53 -0800 [thread overview]
Message-ID: <xmqqsitoefvi.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20131219190333.GE23496@pacific.linksys.moosehall> (Adam Spiers's message of "Thu, 19 Dec 2013 19:03:33 +0000")
Adam Spiers <git@adamspiers.org> writes:
> On Thu, Dec 19, 2013 at 06:36:45PM +0000, Adam Spiers wrote:
>> I wanted to be able to experiment with the TREESAME example given in
>> the git-log(1) man page, so I built this script which recreates it:
>
> [snipped]
>
>> Would it be worth including this in (say) contrib/, and then referring
>> to it from the man page, in case anyone else feels a similar urge?
I doubt it. 75% of the work for such a person to understand the
behaviour from such an example is to understand what kind of history
the example is building. As you noticed, we do have existing tests
to build "interesting" sample histories, but the fact that you did
not bother with them and instead rolled your own should tell us
something ;-) The next person is unlikely to read your sample in
contrib/ but will roll his own, which is probably more efficient way
than learning from a series of commands.
What we _could_ do instead may be to better annotate sample
histories in the existing tests. Some of them (e.g. 6004, 6007) do
have topology illustrations with what paths are changed at each node
in the graph, but many lack such a visual aid to help readers
understand what is going on at a glance.
next prev parent reply other threads:[~2013-12-19 20:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 18:36 script for reproducing history example in git-log(1) man page Adam Spiers
2013-12-19 19:03 ` questions / suggestions about history simplification Adam Spiers
2013-12-19 19:10 ` Jonathan Nieder
2013-12-19 20:38 ` Adam Spiers
2013-12-19 20:20 ` Junio C Hamano
2013-12-19 20:36 ` Adam Spiers
2013-12-19 20:39 ` Junio C Hamano
2013-12-19 20:46 ` Adam Spiers
2013-12-19 20:37 ` Junio C Hamano [this message]
2013-12-19 20:58 ` Adam Spiers
2013-12-22 6:44 ` Junio C Hamano
2013-12-22 13:41 ` Adam Spiers
2013-12-26 9:56 ` Junio C Hamano
2013-12-19 21:04 ` Adam Spiers
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=xmqqsitoefvi.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@adamspiers.org \
--cc=git@vger.kernel.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).