Re: [PATCH v2 2/5] log: honor log.merges= option
- From
- Koosha Khajehmoogahi <koosha@posteo.de>
- Date
- Apr 8, 2015, 10:42 UTC
- Message-ID
- <5525062A.2010905@posteo.de>
- In-Reply-To
- <xmqq4morcq0l.fsf@gitster.dls.corp.google.com>
On 04/08/2015 04:28 AM, Junio C Hamano wrote:
Show 20 quoted lines
> Koosha Khajehmoogahi <koosha@posteo.de> writes: > >> On 04/04/2015 10:00 PM, Junio C Hamano wrote: >>> Koosha Khajehmoogahi <koosha@posteo.de> writes: >>> >>>> From: Junio C Hamano <gitster@pobox.com> >>>> >>>> [kk: wrote commit message] >>> >>> Ehh, what exactly did you write ;-)? >>> >>> I think the most important thing that needs to be explained by the >>> log message for this change is that the variable is honored only by >>> log and it needs to explain why other Porcelain commands in the same >>> "log" family, like "whatchanged", should ignore the variable. >>> >> So, what would be the reason? > > It is strange that you have to ask me to give you the reason why you > chose it that way, isn't it?
AFAIK, the only other command that supports --merges and --no-merges options is rev-list. This new feature aims to make a default behavior for the commands that have these options. The command-line option is supported by the two commands. However, the config var is only used by git-log and rev-list ignores it. I didn't exclude rev-list for any particular reason. If we need, I could also handle it in rev-list.