Re: [PATCH 1/7] Documentation: explain push.default option a bit more
- From
Philip Oakley <philipoakley@iee.org>
- Date
- Apr 23, 2012, 21:01 UTC
- Message-ID
- <7D1315FBD9DC4581BB3C501A53E9E0F8@PhilipOakley>
- In-Reply-To
- <xmqqwr56i7qk.fsf@junio.mtv.corp.google.com>
From: "Junio C Hamano" <gitster@pobox.com> Sent: Monday, April 23, 2012 8:11 PM
Show 24 quoted lines
> "Philip Oakley" <philipoakley@iee.org> writes: > >> From: "Matthieu Moy" <Matthieu.Moy@imag.fr> 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@imag.fr> >>> ... >>> +* `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. >
My mistake. Sorry for the noise / misunderstanding. I now see that [PATCH 6/7] has the change.