Re: Unresolved issues #2

From: Daniel Barkalow <barkalow@iabervon.org>
Date: May 4, 2006, 20:41 UTC
Message-ID: <Pine.LNX.4.64.0605041627310.6713@iabervon.org>
In-Reply-To: <7v4q065hq0.fsf@assigned-by-dhcp.cox.net>

On Thu, 4 May 2006, Junio C Hamano wrote:

Show 7 quoted lines

> * Message-ID: <Pine.LNX.4.63.0604301524080.2646@wbgn013.biozentrum.uni-wuerzburg.de>
> 
>   An optional "git fetch --store newname URL refspecs..." to
>   create an equivalent of remotes file so newname can then be
>   used as a short-hand.  I still have somewhat negative reaction
>   to it, but I am willing to apply it if there are enough people
>   who want this.

I was just about to suggest something for this general use. It's currently kind of a pain to deal with the situation where you've got stuff on your workstation that you want to version control in a shared repository on a server.

I think it shouldn't be on fetch, though; I think a "git remote" command for describing, creating, and modifying remotes would be better, since you also sometimes want to add a "Push:" line.

Maybe:

 git remote <name>: Print info about <name>
 git remote add <name> <URL> [<direction> ...]: create a remote
 git remote <name> <direction> ...: modify a remote

 where <direction> is either:
  pull <remote> <local> or
  push <local> <remote>

	-Daniel
*This .sig left intentionally blank*