git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Summary of discussion on "git push" default change
Date: Wed, 21 Mar 2012 10:54:05 -0700	[thread overview]
Message-ID: <7vr4wl262q.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 7vty1ndcoi.fsf@alter.siamese.dyndns.org

By now it should be obvious that most people would prefer to see the
default behaviour for 'git push' to be something other than matching, even
if you did not read each and every "me too" message.

Actually, we've known it from the beginning. Otherwise, we wouldn't have
made noises about it in the first place ;-).  It was not the primary
objective of the discussion thread to decide if we are going to switch
away from 'matching' by voting (waking up those who are sleeping, so that
they do not have to be surprised with "I didn't know that was happening!"
was).

The new default we are switching to is not about how many people prefer it
for their own use. It is about what default is the least confusing to the
new users.  A default whose behaviour is easy to explain, easy to follow
and easy to understand is the goal. Once people understand what they want
and realize they fall into a minority, it is easy for them to configure
their push.default to something else, like 'matching'. And 'matching' was
a bad default for that purpose; it was the hardest to explain and
understand in the context of the workflows of many new people.

Many people said that they like 'upstream' solely based on their personal
preference, but a few people did justify their preference of 'upstream'
over 'current' based on their experience in teaching new people and
observing the sharp edges that hurt them. And they all sounded reasonable.

In order to show how the world after phase #2 of the transition [*1*]
would look like to developers, testers and early adopters, I am planning
merge Matthieu's patch mm/push-default-switch-warning topic [*2*] to
'next', together with Christopher's ct/advise-push-default topic [*3*];
hopefully these topics can be merged to 'master' soon after 1.7.10 final.

Thanks.

To people who helped spreading the initial RFD message: please do feel
free to distribute this message to the same channels, too.


[References]

*1* http://article.gmane.org/gmane.comp.version-control.git/193308

*2* https://github.com/gitster/git/commit/5293b54

*3* https://github.com/gitster/git/commit/f25950f

  parent reply	other threads:[~2012-03-21 17:54 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17  5:10 Please discuss: what "git push" should do when you do not say what to push? Junio C Hamano
2012-03-17  5:22 ` Junio C Hamano
2012-03-17 10:05   ` Andrew Sayers
2012-03-18 18:50     ` Junio C Hamano
2012-03-18 21:26       ` Ævar Arnfjörð Bjarmason
2012-03-19  0:29         ` Junio C Hamano
2012-03-19  7:29           ` Sebastien Douche
2012-03-19 20:11       ` Andrew Sayers
2012-03-19 21:43         ` Junio C Hamano
2012-03-19 22:20           ` demerphq
2012-03-19 22:38             ` Junio C Hamano
2012-03-20 10:00               ` Andreas Ericsson
2012-03-19 22:47           ` Andrew Sayers
2012-03-19 22:59             ` Junio C Hamano
2012-03-20 21:20               ` Andrew Sayers
2012-03-20 23:09                 ` Junio C Hamano
2012-03-20 23:41                   ` Andrew Sayers
2012-03-21  0:25                     ` Junio C Hamano
2012-03-20 14:12   ` Martin Langhoff
2012-03-20 15:28     ` Junio C Hamano
2012-03-20 18:31       ` Martin Langhoff
2012-03-20 16:43     ` Jakub Narebski
2012-03-21 17:54   ` Junio C Hamano [this message]
2012-03-21 18:05     ` Summary of discussion on "git push" default change Matthieu Moy
2012-03-17 14:00 ` Please discuss: what "git push" should do when you do not say what to push? Joey Hess
2012-03-19  0:36   ` Junio C Hamano
2012-03-17 18:43 ` fREW Schmidt
2012-03-18  4:02   ` H. Peter Anvin
2012-03-18  5:43     ` Marcus D. Hanwell
2012-03-18 16:52   ` Sebastian Schuberth
2012-03-19  9:07 ` Peter Krefting
2012-03-19  9:35   ` Letting remote repositories override local configuration Jonathan Nieder
2012-03-19 12:21     ` Peter Krefting
2012-03-19 18:57 ` Please discuss: what "git push" should do when you do not say what to push? Kevin Ballard
2012-03-20  2:27 ` Antony Male
2012-03-20 12:04   ` Jakub Narebski
2012-03-20 13:04     ` Antony Male
2012-03-20  7:13 ` Nathan Gray
2012-03-20 12:00   ` Ben Tebulin
2012-03-20 12:00   ` Ben Tebulin
2012-03-20 12:00   ` Ben Tebulin
2012-03-20 12:01   ` Ben Tebulin
2012-03-20 12:36 ` Filipe Fernandes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vr4wl262q.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).