From: Stephan Beyer <s-beyer@gmx.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jay Soffian <jaysoffian@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: Are these bugs?
Date: Thu, 28 Aug 2008 03:04:58 +0200 [thread overview]
Message-ID: <20080828010458.GE12354@leksak.fem-net> (raw)
In-Reply-To: <7v1w0akolk.fsf@gitster.siamese.dyndns.org>
Hi,
Junio C Hamano wrote:
> "Jay Soffian" <jaysoffian@gmail.com> writes:
>
> > I understand why "git reset" failed, but at best the error message is
> > confusing to a new user.
>
> This is in "patches welcome" category.
<noise>
I sometimes wondered if "git init" should create a dummy commit
with empty tree, empty commit message or something like that and
set refs/heads/master to that and HEAD to master.
But I always said to myself that this is a stupid idea for several
reasons, i.e. backwards compatibility, or: if the dummy commit is to
be ignored (i.e. will not become parent of the first commit),
then it does not really help at all in decreasing complexity.
So I rejected this thought, but now it came back. ;-)
A backwards-compatibily-breaking dummy commit would also help
rebasing onto the dummy (replacing the first real commit).
But I still think it's stupid.
</noise>
So, for a patch, is it sane to just remove/clear the index
if get_sha1("HEAD", sha1) fails?
Regards,
Stephan
--
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
next prev parent reply other threads:[~2008-08-28 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 23:36 Are these bugs? Jay Soffian
2008-08-27 23:47 ` Junio C Hamano
2008-08-28 1:04 ` Stephan Beyer [this message]
2008-08-28 1:20 ` Junio C Hamano
2008-08-28 8:44 ` Benny Halevy
[not found] ` <76718490808271825j68ac6abch406a8e12b5849b1a@mail.gmail.com>
2008-08-28 1:26 ` Jay Soffian
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=20080828010458.GE12354@leksak.fem-net \
--to=s-beyer@gmx.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@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).