Thread (1 message) 1 message, 1 author, 2016-06-15

Re: git push default behaviour?

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:53:16

Junio C Hamano [off-list ref] writes:
Matthieu Moy [off-list ref] writes:
quoted
Junio C Hamano [off-list ref] writes:
quoted
I can send a message saying "[...]" to the kernel list. Anybody could,
for that matter.
...
But I obviously *WILL* *NOT* be able to do so for *all* communities
whose members may be negatively affected.
Oh, let's avoid any misunderstanding before it happens.

I am not saying that we need to get involvement only from people who
might like the current default.  If you read the "[...]" part you
omitted from your quote again, you will notice that the RFH message was
carefully crafted to take a neutral position, and solicit input from
both sides, and that was very much on purpose.

I was hoping that the reaction to my reply would be that "let's
change the default" folks to help polishing the wording of the RFH
message further, and post the final one to help spreading the word,
both in the forums of projects that will be helped by the change,
and of those that will be irritated by the change.

I didn't mean to suggest anybody to play politics by asking input
from only one side to skew the discussion, even though it is not
like we will decide by majority vote anyway.  Deciding in favor of
whichever position you happen to like is not the goal. Avoiding user
surprises and unnecessary harm is.

And that is why the lesson the older thread from 1.6.3-1.6.4 era
teaches us is important.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help