From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Joel Mahoney <joelmahoney@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: fatal: bad revision 'HEAD'
Date: Thu, 13 Aug 2009 00:38:55 -0400 [thread overview]
Message-ID: <20090813043855.GA21158@coredump.intra.peff.net> (raw)
In-Reply-To: <7v1vngmitn.fsf@alter.siamese.dyndns.org>
On Wed, Aug 12, 2009 at 09:36:04PM -0700, Junio C Hamano wrote:
> I honestly do not know of a sane reason (other than "because I can")
> anybody would want to _start_ a new root in a repository with an existing
> history. And doing a "pull" with or without --rebase immediately after
> starting a new root is doubly insane, as you say.
IIRC, the reason I did it was to throw away history, starting a new root
at the current state. Which is at least a little bit sane, though I
think I might just do it with a graft and filter-branch these days.
> But that is the kind of "ending up to have" I am talking about; it is not
> something you _aim to_ create on purpose. If you want to _start_ a
> separate history, and if you are sane, you would start the separate
> history in a separate repository.
Agreed. Let's not worry about it, then.
-Peff
next prev parent reply other threads:[~2009-08-13 4:39 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 [this message]
2009-08-13 5:02 ` Joel Mahoney
2009-08-13 5:10 ` 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=20090813043855.GA21158@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).