Am 27.03.2015 um 13:27 schrieb Garbageyard:
> We use Gitolite for access control and i have admin access on Git server. I
> wanted to make sure that whenever a new repository is created and is then
> cloned on any machine, the default branch should point to mainline. To do
> this, when I run the repository creation script, i change the content of
> file HEAD of a given repository to point to mainline i.e., default entry of
> “ref: refs/heads/master” in file HEAD is changed to “ref:
> refs/heads/mainline”.
>
> For example, if "work" is the repository name, then on Git server,
>
> [gitolite@gitserver repositories]$ cd work.git/
>
> [gitolite@gitserver work.git]$ cat HEAD
> ref: refs/heads/mainline
>
> If i now clone the repository on my local machine, then the default branch
> should be pointing to mainline and not master. However, the issue is that it
> still points to master. Am I /wrong/ in assuming that changing the entry in
> file HEAD for a given repository on Git server will change the default
> branch while cloning? If I’m wrong, can anyone please tell me how can I
> enforce this change on the /server/ side correctly?
Works for me with "gitolite3 v3.6.2-24-g8e36230 on git 2.3.4".
Could it be that the repo was emtpy when you tried to clone it ?
Stefan
--
----------------------------------------------------------------
/dev/random says: Half of the people in the world are below average.
python -c "print
'73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"
GPG Key fingerprint = 2DF5 E01B 09C3 7501 BCA9 9666 829B 49C5 9221 27AF
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
