git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Gaurav Chhabra <varuag.chhabra@gmail.com>
To: git@vger.kernel.org
Subject: Re: Change default branch name (server side) while cloning a repository
Date: Sun, 29 Mar 2015 13:03:23 +0530	[thread overview]
Message-ID: <CAGDgvc3BWfCOMcQZunq5H0FpP05L3J7bPHpnpM4gJRSkChco2A@mail.gmail.com> (raw)

@Stefan: Thanks for letting me know the version you tried on.

I have the following:
Gitolite version: gitolite3 v3.04-13-gcc9727c-dt on git 1.7.1
Git server version: git version 1.7.1
Git client version: git version 1.9.4.msysgit.2

My Git server version lags quite behind compared to yours. :) Clone of
any repository is not empty because i create non-empty directories
while creating any repository.

@Matthieu: You were right in saying that client can get confused if
several branches point to same commit. :)  Thank a ton! :) Going by
what Jeff mentioned confidently, my server version (1.7.1) indeed has
that flaw.

@Jeff: You've hit the nail on the head! :) Both Matthieu & you are
right. I even confirmed the same by changing the content of mainline
while initializing repository. SHAs indeed became different for both
master and mainline. Now when i clone the repository on my local
machine, it correctly points to mainline. And special thanks for
pointing to the exact Git version where the flaw was fixed. :) I
checked the release notes too. :)

https://git.kernel.org/cgit/git/git.git/tree/Documentation/RelNotes/1.8.4.3.txt

Thank you guys! You rock!!!

             reply	other threads:[~2015-03-29  7:33 UTC|newest]

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

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=CAGDgvc3BWfCOMcQZunq5H0FpP05L3J7bPHpnpM4gJRSkChco2A@mail.gmail.com \
    --to=varuag.chhabra@gmail.com \
    --cc=git@vger.kernel.org \
    /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).