From: demerphq <demerphq@gmail.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 2/3] push: add --current
Date: Mon, 20 Jul 2009 13:17:36 +0200 [thread overview]
Message-ID: <9b18b3110907200417t2e916d9bqffdb168329d88bc4@mail.gmail.com> (raw)
In-Reply-To: <1248071820-18289-3-git-send-email-bonzini@gnu.org>
2009/7/20 Paolo Bonzini <bonzini@gnu.org>:
[snip]
> A secondary effect of --head is that, if there is no push.default
> specified, I make the default push refspec "HEAD".
I think you mean something like:
A secondary effect of --current is that if there is no push.default
configuration setting specified the default push refspec will be "HEAD".
The important point being you talk about --current but then mention
--head which I am guessing was a previous name for this option.
BTW, I like this option and I can imagine it will be a popular alias.
One of the more common questions I get asked from people about git is
what to do about all the "error" messages when pushing. I usually
explain that unless the error message concerns the current branch
which you wanted to push that they can be ignored. I look forward to
pointing out this option instead. Thanks. :-)
Cheers,
yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
next prev parent reply other threads:[~2009-07-20 11:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 6:36 [PATCH 0/3] add push --current and remote.*.pushHeadOnly Paolo Bonzini
2009-07-20 6:36 ` [PATCH 1/3] reintroduce PUSH_DEFAULT_UNSPECIFIED Paolo Bonzini
2009-07-20 6:36 ` [PATCH 2/3] push: add --current Paolo Bonzini
2009-07-20 7:14 ` Björn Steinbrink
2009-07-20 9:48 ` Paolo Bonzini
2009-07-20 10:15 ` Tay Ray Chuan
2009-07-20 11:50 ` Paolo Bonzini
2009-07-20 11:17 ` demerphq [this message]
2009-07-20 6:37 ` [PATCH 3/3] push: add remote.*.pushHeadOnly configuration Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2009-07-20 11:58 [PATCH v3 0/3] add push --current and remote.*.pushHeadOnly Paolo Bonzini
2009-07-20 11:58 ` [PATCH 2/3] push: add --current Paolo Bonzini
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=9b18b3110907200417t2e916d9bqffdb168329d88bc4@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=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).