git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Boris Faure <billiob@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] branch: add optional parameter to -r to specify remote
Date: Mon, 20 Jun 2011 08:40:32 +0200	[thread overview]
Message-ID: <4DFEEB60.5000005@viscovery.net> (raw)
In-Reply-To: <7vtyble9k8.fsf@alter.siamese.dyndns.org>

Am 6/20/2011 0:32, schrieb Junio C Hamano:
> It would make much more sense to restrict this feature to the "listing"
> side of the branches.  It would be nice if you can do:

I agree with everything you said earlier and the first sentence above. And
I would have needed the possibility to limit the branch listing to a
particular remote a lot in the past. But...

> 	$ git branch -r --match alice --match bob
> 
> to show only remote tracking branches under refs/remotes/{alice,bob}
> and also
> 
> 	$ git branch --match "jk/*"
> 
> to show only local topic branches whose names match the given blob.

I would hate having to learn a new syntax '--match "jk/*"' when we can
already say

    $ git log --remotes
    $ git log --remotes=alice --remotes=bob
    $ git log --remotes="jk/*"

IMO, it is the right approach to have a long option --remotes with an
optional argument.

-- Hannes

  reply	other threads:[~2011-06-20  6:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19 19:19 [PATCH/RFC] branch: add optional parameter to -r to specify remote Boris Faure
2011-06-19 19:19 ` Boris Faure
2011-06-19 22:32   ` Junio C Hamano
2011-06-20  6:40     ` Johannes Sixt [this message]
2011-06-20  7:03       ` Jeff King
2011-06-20 11:08         ` Michael J Gruber
2011-06-20 13:09           ` Jeff King
2011-06-20 15:42             ` Junio C Hamano
2011-06-20 16:59               ` [PATCH] tag: accept multiple patterns for --list Jeff King
2011-06-20 15:49           ` [PATCH/RFC] branch: add optional parameter to -r to specify remote Junio C Hamano
2011-06-20 15:39         ` Junio C Hamano
2011-06-20 19:12     ` Boris Faure

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=4DFEEB60.5000005@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=billiob@gmail.com \
    --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).