git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>
To: Garbageyard <varuag.chhabra@gmail.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Change default branch name (server side) while cloning a repository
Date: Fri, 27 Mar 2015 15:27:27 +0100	[thread overview]
Message-ID: <551568CF.2050301@atlas-elektronik.com> (raw)
In-Reply-To: <1427459241861-7627964.post@n2.nabble.com>

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

  reply	other threads:[~2015-03-27 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 12:27 Change default branch name (server side) while cloning a repository Garbageyard
2015-03-27 14:27 ` Stefan Näwe [this message]
2015-03-27 16:47   ` Jeff King
2015-03-27 16:40 ` Matthieu Moy
  -- strict thread matches above, loose matches on Subject: below --
2015-03-29  7:33 Gaurav Chhabra

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=551568CF.2050301@atlas-elektronik.com \
    --to=stefan.naewe@atlas-elektronik.com \
    --cc=git@vger.kernel.org \
    --cc=varuag.chhabra@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).