Ilya Bobyr ilya.bo...@gmail.com writes:
There is a git remote set-head to manipulate HEAD in a remote repository.
This is misleading. The command does nothing on the remote side, it
only changes the refs/remote namespace in your repository. The purpose
is to change what branch the ref
On 03/09/2014 07:46 AM, Torsten Bögershausen wrote:
After creating a local repository with these two branches, and a server
repository with git init --bare, and pushing the two branches:
git remote add originfoo@bar:~/path/test.git
git push origin master-g
git push origin master-x
HEAD on the remote repo is indeed used to determine what to check out
when cloning. It's quite normal to change it to anything you like. To
change it, you usually use git symbolic-ref HEAD master-x instead of
directly editing that file.
On Sun, Mar 9, 2014 at 8:54 PM, Carlos Pereira
On 3/9/2014 12:54 PM, Carlos Pereira wrote:
On 03/09/2014 07:46 AM, Torsten Bögershausen wrote:
After creating a local repository with these two branches, and a
server repository with git init --bare, and pushing the two branches:
git remote add originfoo@bar:~/path/test.git
git push
There is a git remote set-head to manipulate HEAD in a remote
repository.
Thanks, that is useful (like git symbolic-ref HEAD master-x suggested by
Kevin, much better than editing the text file)
I agree that this might be viewed as a user experience issue.
But I can not come up with a possible
Hi,
git newbie here.
I would like to work with two main branches: master-g and master-x,
instead of the usual master, and apparently git does not like this.
After creating a local repository with these two branches, and a server
repository with git init --bare, and pushing the two branches:
On 2014-03-08 22.37, Carlos Pereira wrote:
Hi,
git newbie here.
I would like to work with two main branches: master-g and master-x, instead
of the usual master, and apparently git does not like this.
After creating a local repository with these two branches, and a server
repository
7 matches
Mail list logo
