Git development
 help / color / mirror / Atom feed
From: Johannes Sixt <johannes.sixt@telecom.at>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Teach git-remote to list pushed branches.
Date: Wed, 21 Mar 2007 00:27:32 +0100	[thread overview]
Message-ID: <200703210027.32307.johannes.sixt@telecom.at> (raw)
In-Reply-To: <7v648wg8sy.fsf@assigned-by-dhcp.cox.net>

On Monday 19 March 2007 23:36, Junio C Hamano wrote:
> *1* Actually I think the refspec list on "Push: " lines should
> be split out into separate array elements, because
>
> 	Push: A B C
>
> is equivalent to
>
> 	Push: A
>         Push: B
>         Push: C
>
> This does not apply to "Pull: " lines, as
>
> 	Pull: A B C
>
> and
>
> 	Pull: A
> 	Pull: B
> 	Pull: C
>
> mean quite different things.
>
> This distinction does not matter to the current callers, but I
> was hoping that somebody would build "interactive" mode to edit
> Push and Pull list, and when that happens, having A B C as
> separate entries in @{$hash->{$name}{'PUSH'}} would be handier
> to code.

The patch does just that, I think. It is only that everything is *printed* on 
one line, just like the tracked branches.

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).

-- Hannes

  reply	other threads:[~2007-03-20 23:27 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 [this message]
2007-03-21  3:03         ` Junio C Hamano
  -- 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=200703210027.32307.johannes.sixt@telecom.at \
    --to=johannes.sixt@telecom.at \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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