From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Steffen Prohaska <prohaska@zib.de>,
Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: [PATCH] fix "git push $there +HEAD"
Date: Wed, 20 Feb 2008 13:02:19 +0000 (GMT) [thread overview]
Message-ID: <alpine.LSU.1.00.0802201301230.17164@racer.site> (raw)
In-Reply-To: <7vprurc3n8.fsf@gitster.siamese.dyndns.org>
Hi,
On Wed, 20 Feb 2008, Junio C Hamano wrote:
> An earlier commit 47d996a (push: support pushing HEAD to real branch
> name) added support for "git push $there HEAD" by introducing a rewrite
> rule for the refspecs obtained from the command line. However, unlike
> the usual refspecs, it did not allow prefixing with '+' to mean forcing
> the branch.
Heh. I realised that yesterday, and put it in my TODO list. Thanks for
doing it for me! ;-)
The patch looks obviously correct to me.
Ciao,
Dscho
next prev parent reply other threads:[~2008-02-20 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 10:40 [PATCH] fix "git push $there +HEAD" Junio C Hamano
2008-02-20 13:02 ` Johannes Schindelin [this message]
2008-02-20 17:59 ` Daniel Barkalow
2008-02-20 18:16 ` 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=alpine.LSU.1.00.0802201301230.17164@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=prohaska@zib.de \
/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).