From: Junio C Hamano <junkio@cox.net>
To: Johannes Sixt <johannes.sixt@telecom.at>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Teach git-remote to list pushed branches.
Date: Tue, 20 Mar 2007 20:03:58 -0700 [thread overview]
Message-ID: <7v1wjj70wx.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200703210027.32307.johannes.sixt@telecom.at> (Johannes Sixt's message of "Wed, 21 Mar 2007 00:27:32 +0100")
Johannes Sixt <johannes.sixt@telecom.at> writes:
> BTW, the .git/remotes parser does not allow multiple refspecs on one 'Push:'
> line, if I understand it correctly (I'm looking at get_remotes_uri in
> builtin-push.c).
Sheesh, you are right. That is a regression introduced, when
git-push was rewritten as a built-in, and I did not know about
it until now.
next prev parent reply other threads:[~2007-03-21 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 20:34 [PATCH] Teach git-remote to list pushed branches Johannes Sixt
2007-03-18 20:37 ` Junio C Hamano
2007-03-19 19:16 ` Johannes Sixt
2007-03-19 22:36 ` Junio C Hamano
2007-03-20 23:27 ` Johannes Sixt
2007-03-21 3:03 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-14 20:56 Johannes Sixt
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=7v1wjj70wx.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=johannes.sixt@telecom.at \
/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