From: Andreas Ericsson <ae@op5.se>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/4] Default to displaying /all/ non-tag refs, not just locals
Date: Fri, 03 Nov 2006 11:55:56 +0100 [thread overview]
Message-ID: <454B203C.9040006@op5.se> (raw)
In-Reply-To: <200611030847.22252.andyparkins@gmail.com>
Andy Parkins wrote:
> On Friday 2006 November 03 02:40, Junio C Hamano wrote:
>
>> That is a change in behaviour and given that we introduced
>> remotes for the explicit purpose of not to clutter the local
>> branch namespace, I doubt defaulting to _show_ remotes is a good
>
> Really? I had imagined it was to prevent accidental checking out of an
> upstream-tracking branch. Also; I don't think "not cluttering the namespace"
> is the same as "not showing multiple namespaces". The local namespace
> remains as uncluttered as it ever was. This is a question of what to
> display.
>
> Assuming my "mixed mode" display thing were in place, doesn't that make the
> two choices of UI
>
> 1)
> git-branch : show local branches
> git-branch --all : show local and remote branches
> git-branch -r : show remote branches
> 2)
> git-branch : show local and remote branches
> git-branch --local : show local branches
> git-branch -r : show remote branches
>
> In case 2) the switch is simply selecting a filter, and so fits in with
> the "-r" better.
>
I think it'd make more sense if git-branch could instead take a --filter
parameter that does a simple strncmp(filter, branch, strlen(filter)) to
see if it should show a branch or not. That way, "--filter=remotes"
would work splendidly. "local" as keyword to "--filter" could possibly
be a special case and need documentation.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
next prev parent reply other threads:[~2006-11-03 10:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bec6ab7849e3fcacac23cca44a0ba93282af5fca.1162465753.git.andyparkins@gmail.com>
2006-11-02 11:11 ` [PATCH 2/4] Rename remote_only to display_mode Andy Parkins
2006-11-03 2:40 ` Junio C Hamano
2006-11-03 8:40 ` Andy Parkins
2006-11-03 10:51 ` Andreas Ericsson
2006-11-03 11:51 ` Junio C Hamano
2006-11-03 12:37 ` Andy Parkins
2006-11-03 12:00 ` Andy Parkins
2006-11-03 13:23 ` Andreas Ericsson
2006-11-03 10:52 ` [PATCH] Add support to git-branch to show local and remote branches Andy Parkins
2006-11-03 12:06 ` [PATCH] Colourise git-branch output Andy Parkins
2006-11-03 19:25 ` Junio C Hamano
2006-11-03 23:05 ` Alex Riesen
2006-11-03 12:08 ` [PATCH] Add support to git-branch to show local and remote branches Junio C Hamano
2006-11-03 12:40 ` Andy Parkins
2006-11-03 19:19 ` Junio C Hamano
2006-11-02 11:11 ` [PATCH 3/4] Default to displaying /all/ non-tag refs, not just locals Andy Parkins
2006-11-03 2:40 ` Junio C Hamano
2006-11-03 8:47 ` Andy Parkins
2006-11-03 10:55 ` Andreas Ericsson [this message]
2006-11-02 11:11 ` [PATCH 4/4] Show the branch type after the branch name for remotes Andy Parkins
2006-11-03 2:40 ` Junio C Hamano
2006-11-03 8:33 ` Andy Parkins
2006-11-03 20:08 ` 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=454B203C.9040006@op5.se \
--to=ae@op5.se \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
/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).