Re: questions / suggestions about history simplification

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 ;-)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]