From: Adam Spiers <git@adamspiers.org>
To: git mailing list <git@vger.kernel.org>
Subject: Re: questions / suggestions about history simplification
Date: Thu, 19 Dec 2013 21:04:48 +0000 [thread overview]
Message-ID: <20131219210448.GK23496@pacific.linksys.moosehall> (raw)
In-Reply-To: <20131219190333.GE23496@pacific.linksys.moosehall>
On Thu, Dec 19, 2013 at 07:03:33PM +0000, Adam Spiers wrote:
> I still don't understand a few things about history simplification:
>
> 1. The "--full-history without parent rewriting" correctly asserts
> that commit Q will be shown. But AFAICS this contradicts the
> documented behaviour "Commits are included if they are not TREESAME
> to any parent" which is implied by "This mode differs from the
> default in one point:", because Q is TREESAME to P.
I'm *guessing* that this apparent exception to the stated rules could
be because Q is the start of the walk. Or maybe I'm just missing a
key detail. I'd love to hear confirmation either way.
[Questions 2 and 3 snipped]
4. --dense (the default behaviour) includes walked commits iff they are not
TREESAME to any parent. --sparse includes all walked commits. But
how do I get the middle ground, i.e. all walked commits which are
not TREESAME to at least one parent?
This seems like an obvious use case, but I haven't figured out how to
do it yet :-/
Thanks! (I probably don't say that often enough, but the sentiment is
always there ;-)
prev parent reply other threads:[~2013-12-19 21:04 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
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 [this message]
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=20131219210448.GK23496@pacific.linksys.moosehall \
--to=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