Re: [PATCH 1/7] Documentation: explain push.default option a bit more

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

 



"Philip Oakley" <philipoakley@xxxxxxx> writes:

> From: "Matthieu Moy" <Matthieu.Moy@xxxxxxx> Sent: Monday, April 23,
> 2012 9:37 AM
>> The previous documentation was explaining _what_ the options were doing,
>> but were of little help explaining _why_ a user should set his default to
>> either of the options.
>>
>> Signed-off-by: Matthieu Moy <Matthieu.Moy@xxxxxxx>
>> ...
>> +* `matching` - push all branches having the same name in both ends.
>> + ...
>> +  updated the branch remotely. This is the default.
>
> Given the expected future change to 'simple' as the default, surely
> "This is currently the default." give the hint toward that change.

Correct, and that is exactly why this patch does not say "currently".

As the proposed commit log message explains, this change is about
clarifying what these options are and unrelated to "future" default
change at all at this step.
--
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]