Re: [PATCH] revision: --ancestry-path
- From
Johannes Sixt <j.sixt@viscovery.net>
- Date
- Apr 21, 2010, 07:47 UTC
- Message-ID
- <4BCEADA3.7090504@viscovery.net>
- In-Reply-To
- <201004210934.30226.johan@herland.net>
Am 4/21/2010 9:34, schrieb Johan Herland:
Show 5 quoted lines
> I can confirm that this patch works with my original (more complicated) > scenario. I've also played around with combinations of --ancestry-path, -- > graph and --parents (and even --boundary), and AFAICS, the new option does > not clobber the other options, and (IMHO) it all behaves correctly in the > scenarios I've tested.
How about possible interactions with --reverse; --date-order/--topo-order, --parents (important for gitk); --simplify-by-decoration (useful for your problem that triggered this); --full-history and --simplify-merges with path limiting?
-- Hannes