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

"Philip Oakley" [off-list ref] writes:

From: "Matthieu Moy" <redacted> Sent: Monday, April 23,
2012 9:37 AM

quoted

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 <redacted>
...
+* `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.

From: "Junio C Hamano" <redacted>  Sent: Monday, April 23, 2012 
8:11 PM

"Philip Oakley" [off-list ref] writes:

quoted

From: "Matthieu Moy" <redacted> Sent: Monday, April 23,
2012 9:37 AM

quoted

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 <redacted>
...
+* `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.