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:20:52 -0800 [thread overview]
Message-ID: <xmqq38lofv8b.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:
> 2. What difference does --dense ever make?
It is set by default, and --sparse is its opposite option, i.e. it
turns revs->dense off.
When revs->dense is turned off, the usual treesame logic does not
kick in to rewrite parents in a single strand of pearls (i.e. a
stretch of history that solely consists of non-merge commits).
> 3. Why is --sparse so called, given that it increases rather than
> decreases the number of commits shown?
The number of commits in the output will increase by including
commits that are irrelevant to explain the history of paths
specified by pathspec in revs->prune. The information density
decreases as the result, and that is what "sparse" signifies.
next prev parent reply other threads:[~2013-12-19 20:21 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 [this message]
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
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=xmqq38lofv8b.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.