Re: fatal: bad revision 'HEAD'

From: Jeff King <peff@peff.net>
Date: Aug 13, 2009, 05:10 UTC
Message-ID: <20090813051058.GA25830@coredump.intra.peff.net>
In-Reply-To: <89456E84-1A85-4D0C-9643-C191EE877E61@gmail.com>

On Wed, Aug 12, 2009 at 11:02:45PM -0600, Joel Mahoney wrote:

Show 11 quoted lines

> I'm not sure I completely understand where you guys are at with this
> thread : - ) but I thought I would mention that the question arose
> from my inability to install a plugin into a Ruby on Rails project
> based on my having (unknowingly) set branch.master.rebase = true.
>
> I bring this up because a lot of people are getting their first
> exposure to git through Rails/github, and installing plugins in Rails
> is (I think) a good example of brining an existing history (the
> plugin) into a separate repository (your project).  and because this
> maneuver is built into the "./script/plugin install" action, it is
> not something that cannot be easily customized.

Yes, the discussion moved away bit from your original issue. To summarize what is happening:

  - Setting branch.master.rebase in your ~/.gitconfig is probably not a
    good idea, as that tends to be a per-repository property, anyway.
    You can work around the problem for now by removing it.

  - Junio has committed a patch to fix the bug. It will definitely be in
    v1.6.5. If this is a common setup for Rails people, maybe we should
    consider putting it into 'maint' for v1.6.4.1.

-Peff