git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <Kalle.Valo@iki.fi>
To: Amos Waterland <apw@rossby.metr.ou.edu>
Cc: junkio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH] Add git-branches-script
Date: Tue, 16 Aug 2005 20:53:49 +0300	[thread overview]
Message-ID: <87hddplqdu.fsf@litku.valo.iki.fi> (raw)
In-Reply-To: 20050815204430.GA77829@rossby.metr.ou.edu

Amos Waterland <apw@rossby.metr.ou.edu> writes:

> For people whose workflow involves switching back and forth between a
> lot of branches, it can be really helpful to be able to quickly tell
> which branch you are on and which ones are available.  This patch
> introduces a small script that when invoked as `git branches' prints a
> list of available branches with a star in front of the one you are on:
>
>  $ cd linux-2.6/
>  $ git checkout -b ppc64-cleanups
>  $ git checkout -b ppc64-new-devel
>  $ git checkout -b ppc64-all-merge
>  $ git branches
>    master
>  * ppc64-all-merge
>    ppc64-cleanups
>    ppc64-new-devel

I would prefer to using some git command compared to 'ls -l
.git/refs/heads/'. In my opinion there is a need for this command and
it should be included.

But my immediate concern was that there is already 'git branch'
command and 'git branches' is too similar. I think they should be
merged. I have a patch coming up.

-- 
Kalle Valo

  reply	other threads:[~2005-08-16 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 20:44 [PATCH] Add git-branches-script Amos Waterland
2005-08-16 17:53 ` Kalle Valo [this message]
2005-08-16 17:58   ` [PATCH] Change git-branch to list branches Kalle Valo
2005-08-16 21:08     ` Junio C Hamano
2005-08-17 19:48       ` Kalle Valo
2005-08-17 20:15         ` Kalle Valo
2005-08-17 20:37 ` [PATCH] Add git-branches-script Miguel Bazdresch

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=87hddplqdu.fsf@litku.valo.iki.fi \
    --to=kalle.valo@iki.fi \
    --cc=apw@rossby.metr.ou.edu \
    --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;
as well as URLs for NNTP newsgroup(s).