Re: [PATCH] cg-pull to stop treating "master" specially, fix fetch_local for .git/HEAD
- From
- Josef Weidendorfer <josef.weidendorfer@gmx.de>
- Date
- Nov 10, 2005, 23:26 UTC
- Message-ID
- <200511110026.18324.Josef.Weidendorfer@gmx.de>
- In-Reply-To
- <1124832796.23795.9.camel@dv>
On Tuesday 23 August 2005 23:33, Pavel Roskin wrote:
Show 7 quoted lines
> Hello! > > This patch changes cg-pull so that if the branch is not specified, it > takes origin's .git/HEAD without first trying .git/refs/heads/master. > This removes preferential treatment of the "master" branch, allowing the > upstream to use another name for the default branch. To get the master > branch, users would have to append "#master" to the URL.
I think this is wrong.
Why would anybody want to fetch the current upstream HEAD at cg-pull time? If you do this, and you have no control on the upstream repository, "origin" will jump randomly around after cg-pull, depending on the current HEAD of the origin repository.
Besides, this is a incompatible change in cg-pull behavior: I am sure that a lot of people did a cg-clone in the past without any specific remote branch, and expect that cg-pull will update their origin to the remote "master". Now, if they update to a new Cogito with this patch, the next cg-pull sometimes will rebase their origin to another random branch, depending on remote HEAD ?!
Or am I missing something here?
Josef