From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Greg Jacobson <coder5000@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH v3] push: Enhance unspecified push default warning
Date: Tue, 5 Nov 2013 11:16:59 +0100 (CET) [thread overview]
Message-ID: <1839883487.4893076.1383646619137.JavaMail.root@imag.fr> (raw)
In-Reply-To: <xmqqvc08yq4v.fsf@gitster.dls.corp.google.com>
----- Original Message -----
> Greg Jacobson <coder5000@gmail.com> writes:
>
> > Is there anything I could do to improve this patch? Thank you.
>
> My vague recollection is that we started from an excerpt from the
> documentation page, not unlike this patch attempts to, but because
> such an excerpt has to be less complete than the documentation for
> brevity's sake, it is bound to be an incorrect and/or misleading
> one, and decided that we are better off referring the users, who do
> want to choose something other than the default we chose, to the
> documentation.
>
> Somebody cares to dig up the old discussion threads and post a few
> pointers?
The previous versions of this patch received only minor comments,
which were taken into account:
http://thread.gmane.org/gmane.comp.version-control.git/235675
http://thread.gmane.org/gmane.comp.version-control.git/235694
I don't remember all the discussions on the patch which introduced
the warning, but I don't think it's relevant to digg them before applying the patch:
* The assumption was that users would read the docs, but as I already mentioned:
"Judging by the question asked on stackoverflow
( http://stackoverflow.com/questions/13148066/warning-push-default-is-unset-its-implicit-value-is-changing-in-git-2-0 )
and its popularity, telling the users to read the docs did not work very
well."
* The warning has been there for a while now. Advanced users have already set push.default.
We shouldn't be worried about eating a bit of screen real estate for users who didn't yet.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-11-05 10:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 14:20 [PATCH v3] push: Enhance unspecified push default warning Greg Jacobson
2013-11-03 13:35 ` Greg Jacobson
2013-11-04 18:32 ` Junio C Hamano
2013-11-05 10:16 ` Matthieu Moy
2013-11-05 10:16 ` Matthieu Moy [this message]
2013-11-06 19:01 ` Junio C Hamano
2013-11-06 20:10 ` Junio C Hamano
2013-11-06 22:55 ` Junio C Hamano
2013-11-06 21:49 ` Matthieu Moy
2013-11-06 23:45 ` Jonathan Nieder
2013-11-07 10:52 ` Matthieu Moy
2013-11-07 18:14 ` Junio C Hamano
2013-11-07 18:51 ` Matthieu Moy
2013-11-08 18:02 ` Junio C Hamano
2013-11-08 18:56 ` Junio C Hamano
2013-11-08 22:39 ` Marc Branchaud
2013-11-11 17:02 ` Junio C Hamano
2013-11-11 17:03 ` Jonathan Nieder
2013-11-11 17:17 ` Marc Branchaud
2013-11-11 21:12 ` Matthieu Moy
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=1839883487.4893076.1383646619137.JavaMail.root@imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=coder5000@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).