git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Buchacher <drizzd@aon.at>
To: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Junio C Hamano <gitster@pobox.com>,
	Christopher Tiwald <christiwald@gmail.com>,
	git@vger.kernel.org, peff@peff.net
Subject: Re: [PATCH] push: Provide situational hints for non-fast-forward errors
Date: Thu, 15 Mar 2012 09:54:26 +0100	[thread overview]
Message-ID: <20120315085426.GA11003@ecki> (raw)
In-Reply-To: <20120314142752.GD28595@in.waw.pl>

On Wed, Mar 14, 2012 at 03:27:52PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Mar 14, 2012 at 02:00:38PM +0100, Matthieu Moy wrote:
> > Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> writes:
> > 
> > > I think that having three different config keys for the three
> > > different advices makes sense, because the advices will be displayed
> > > at different times.
> > 
> > I don't think it really makes sense to be such fine-grained. We already
> > have 6 different advices, so an advance user who do not want them need
> > to set these 6 variables. I think we want to keep this number relatively
> > low.
> > 
> > The advice messages do not point explicitely to the way to disable them,
> > so users who know how to set advice.* are users who know a little about
> > configuration files, and who read the docs. 
> 
> Elsewhere in this thread it was proposed to add an actual 'git config'
> command to the advice.

The proposed command does not turn off the advice. It only changes
push.default. The advice about push.default is effectively disabled once
they change push.default, but the other warnings are still in effect.

  parent reply	other threads:[~2012-03-15  8:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 23:22 [PATCH] push: Provide situational hints for non-fast-forward errors Christopher Tiwald
2012-03-14  4:27 ` Junio C Hamano
2012-03-14 12:14   ` Zbigniew Jędrzejewski-Szmek
2012-03-14 13:00     ` Matthieu Moy
2012-03-14 14:27       ` Zbigniew Jędrzejewski-Szmek
2012-03-14 16:40         ` Christopher Tiwald
2012-03-15  8:54         ` Clemens Buchacher [this message]
2012-03-15 18:06           ` Junio C Hamano
2012-03-16  8:19             ` Matthieu Moy
2012-03-14 14:48   ` Christopher Tiwald
2012-03-14 14:53     ` Christopher Tiwald
2012-03-14  9:06 ` Matthieu Moy
2012-03-14 15:52   ` Christopher Tiwald
2012-03-14 17:26   ` Junio C Hamano
2012-03-16  5:36     ` Junio C Hamano
2012-03-16  9:10       ` Clemens Buchacher
2012-03-16 12:03         ` Junio C Hamano
2012-03-16 17:20           ` Christopher Tiwald
2012-03-16 18:07             ` Junio C Hamano
2012-03-16 22:00               ` Junio C Hamano
2012-03-16 21:41           ` Clemens Buchacher
2012-03-16 21:53             ` Junio C Hamano
2012-03-16 22:01               ` Clemens Buchacher
2012-03-16 22:10                 ` Junio C Hamano
2012-03-17 17:10       ` [fixup PATCH] " Zbigniew Jędrzejewski-Szmek
2012-03-17 18:46         ` Christopher Tiwald
2012-03-17 19:42           ` Zbigniew Jędrzejewski-Szmek
2012-03-19  0:15           ` Junio C Hamano

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=20120315085426.GA11003@ecki \
    --to=drizzd@aon.at \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=christiwald@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=zbyszek@in.waw.pl \
    /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).