From: Paolo Bonzini <bonzini@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: push.default???
Date: Mon, 22 Jun 2009 19:55:30 +0200 [thread overview]
Message-ID: <4A3FC592.10401@gnu.org> (raw)
In-Reply-To: <7vws74cjrl.fsf@alter.siamese.dyndns.org>
> You cannot do anything "in 1.6.3"; The ship has already left the port.
Yes, that was me reasoning out loud.
>> 4) in 1.6.4 or 1.7.0, make "git push" fail outright if there is no
>> push line, with text suggesting
>
> This was already part of one possible option for push.default (change the
> built-in default to 'nothing-and-warn') when it was introduced, wasn't it?
> Instead of suggesting to configure remote.$name.push, it would suggest to
> set push.default to a desired value, which I think is a more sensible
> thing to do.
Yes, that was also reasoning out loud. It makes sense.
Anyway, suggestion will be helpful for the "tracking" behavior refspec
syntax.
Thanks for the remarks,
Paolo
next prev parent reply other threads:[~2009-06-22 17:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 10:02 push.default??? Paolo Bonzini
2009-06-22 16:31 ` push.default??? Junio C Hamano
2009-06-22 17:55 ` Paolo Bonzini [this message]
2009-06-23 10:34 ` push.default??? Finn Arne Gangstad
2009-06-23 12:59 ` push.default??? Paolo Bonzini
2009-06-23 13:11 ` push.default??? Finn Arne Gangstad
2009-06-23 13:21 ` push.default??? Andreas Ericsson
2009-06-23 13:57 ` push.default??? Finn Arne Gangstad
2009-06-23 14:07 ` push.default??? Andreas Ericsson
2009-06-23 13:28 ` push.default??? Paolo Bonzini
2009-06-23 14:48 ` push.default??? Finn Arne Gangstad
2009-06-23 16:32 ` push.default??? Paolo Bonzini
2009-06-23 17:51 ` push.default??? Junio C Hamano
2009-06-23 17:59 ` push.default??? Junio C Hamano
2009-06-24 5:50 ` push.default??? Miles Bader
2009-06-24 6:35 ` push.default??? Junio C Hamano
2009-06-24 8:50 ` push.default??? Paolo Bonzini
2009-06-24 21:59 ` push.default??? Finn Arne Gangstad
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=4A3FC592.10401@gnu.org \
--to=bonzini@gnu.org \
--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).