git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Joel Mahoney <joelmahoney@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: fatal: bad revision 'HEAD'
Date: Thu, 13 Aug 2009 01:10:58 -0400	[thread overview]
Message-ID: <20090813051058.GA25830@coredump.intra.peff.net> (raw)
In-Reply-To: <89456E84-1A85-4D0C-9643-C191EE877E61@gmail.com>

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

> 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

      reply	other threads:[~2009-08-13  5:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-09 21:15 fatal: bad revision 'HEAD' Joel Mahoney
2009-08-10  1:18 ` Jeff King
     [not found]   ` <09EE2E57-626B-4686-A6DD-3B8DF1BC3FE2@gmail.com>
     [not found]     ` <20090811015615.GA8383@coredump.intra.peff.net>
     [not found]       ` <C44788EB-02BA-4D69-8091-9E97827223A0@gmail.com>
2009-08-12  3:27         ` Jeff King
2009-08-12  7:37           ` Junio C Hamano
2009-08-12  7:58             ` Jeff King
2009-08-12 22:49               ` Junio C Hamano
2009-08-13  2:31                 ` Jeff King
2009-08-13  4:36                   ` Junio C Hamano
2009-08-13  4:38                     ` Jeff King
2009-08-13  5:02                       ` Joel Mahoney
2009-08-13  5:10                         ` Jeff King [this message]

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=20090813051058.GA25830@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=joelmahoney@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.
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 NNTP newsgroup(s).