From: "Shawn O. Pearce" <spearce@spearce.org>
To: Adam Megacz <adam@megacz.com>
Cc: git@vger.kernel.org
Subject: Re: "warning: Updating the currently checked out branch may cause confusion" on bare repositories
Date: Tue, 19 Jan 2010 10:59:06 -0800 [thread overview]
Message-ID: <20100119185906.GF23466@spearce.org> (raw)
In-Reply-To: <xuu2my093owy.fsf@nowhere.com>
Adam Megacz <adam@megacz.com> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
> > That should already be the case. Did you create the bare repository
> > by taking a copy of a non-bare's .git directory? Check your bare
> > repository's config file and see if core.bare = false, if so set
> > it to true to signal it really is bare.
>
> Hrm, is there a reason why this is explicitly configured rather than
> detected?
I don't know why we do this. I think its because the guessing
logic can guess wrong sometimes.
> I was under the impression that you could create a bare repository by
> simply throwing away the working tree and renaming ".git" to any other
> name, but I guess I was wrong.
If you delete the setting from the configuration file, Git usually
almost always guesses correctly. :-)
Its rare to see it fail. But I think it can fail if you create
a file called HEAD in the top level of your source code tree.
(For example.)
--
Shawn.
next prev parent reply other threads:[~2010-01-19 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 22:41 "warning: Updating the currently checked out branch may cause confusion" on bare repositories Adam Megacz
2010-01-19 6:29 ` Shawn O. Pearce
2010-01-19 18:55 ` Adam Megacz
2010-01-19 18:59 ` Shawn O. Pearce [this message]
2010-01-19 22:43 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100119185906.GF23466@spearce.org \
--to=spearce@spearce.org \
--cc=adam@megacz.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.