All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Wishlist for branch management
Date: Mon, 1 Feb 2010 10:19:07 +0100	[thread overview]
Message-ID: <20100201091907.GJ9553@machine.or.cz> (raw)
In-Reply-To: <4B662BEF.7040503@zytor.com>

On Sun, Jan 31, 2010 at 05:18:39PM -0800, H. Peter Anvin wrote:
> A wishlist for better handling of branches:
> 
> git clone --branches
> 
> ... git clone, with the additional step of setting up local branches for
> each one of the remote branches.

Yes please! ;-) However, there should be a corresponding command to do
this with a remote within existing repository. Perhaps something like

	git remote populate

(stealing some syntax from topgit ;-).

> git branch --current
> 
> ... list the current branch name, for use in scripts.  Equivalent to:
> 	"git branch | grep '^\*' | cut -c3-"

I'm used to git symbolic-ref HEAD. I like the fact that human-friendly
and scripting interfaces are mostly separated to different commands.
This also has saner behaviour when HEAD is not on a branch. (Which is
also a reason why operation like this should be done only when there's
a damn good reason to need to know the branch name.)

> git push --current
> 
> ... push the current branch, and only the current branch...

Yes. Even in the HEAD form, it would be nice to have something that does
not require me to write out 'origin' or whatever my remote default is.
Perhaps `git push - HEAD`. There's certain disparity, we have an alias
for the current branch (HEAD) but not for the current remote.

P.S.: I know. It's all just bikeshedding without patches...

-- 
				Petr "Pasky" Baudis
If you can't see the value in jet powered ants you should turn in
your nerd card. -- Dunbal (464142)

  parent reply	other threads:[~2010-02-01  9:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01  1:18 Wishlist for branch management H. Peter Anvin
2010-02-01  1:31 ` Björn Steinbrink
2010-02-01  3:22   ` H. Peter Anvin
2010-02-01  9:19 ` Petr Baudis [this message]
2010-02-01 17:49   ` H. Peter Anvin

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=20100201091907.GJ9553@machine.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.