From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
Ping Yin <pkufranky@gmail.com>, Jeff King <peff@peff.net>,
Johan Herland <johan@herland.net>,
A Large Angry SCM <gitzilla@gmail.com>, git <git@vger.kernel.org>
Subject: Re: What should "git submodule summary" give before an initial commit?
Date: Thu, 4 Mar 2010 07:36:20 +0100 [thread overview]
Message-ID: <fabb9a1e1003032236x59a781b8ne0266877db25d001@mail.gmail.com> (raw)
In-Reply-To: <7vfx4gfvwv.fsf@alter.siamese.dyndns.org>
Heya,
On Thu, Mar 4, 2010 at 07:22, Junio C Hamano <gitster@pobox.com> wrote:
> I think "git reset HEAD" _should_ fail, but on the other hand, "git reset"
> and "git reset paths..." would be Ok before HEAD points at a commit.
Yes, that's what I came up with after sending my email, commands that
_default_ to HEAD as revision should instead default to an empty
commit when there is no HEAD yet. Perhaps something we can add to
parse_opt and then make sure that all commands we care about use that
feature?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-03-04 6:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 12:21 Latest master failing t7401 submodule tests A Large Angry SCM
2010-03-03 19:45 ` Junio C Hamano
2010-03-03 20:02 ` Jeff King
2010-03-03 20:32 ` Junio C Hamano
2010-03-03 20:42 ` Jeff King
2010-03-03 21:04 ` Junio C Hamano
2010-03-03 21:28 ` Junio C Hamano
2010-03-03 21:58 ` What should "git submodule summary" give before an initial commit? Junio C Hamano
2010-03-03 23:10 ` Johan Herland
2010-03-04 0:36 ` Jens Lehmann
2010-03-04 6:01 ` Sverre Rabbelier
2010-03-04 6:22 ` Junio C Hamano
2010-03-04 6:36 ` Sverre Rabbelier [this message]
2010-03-04 6:43 ` Junio C Hamano
2010-03-04 6:48 ` Sverre Rabbelier
2010-03-03 22:57 ` Latest master failing t7401 submodule tests Jeff King
2010-03-03 20:52 ` Junio C Hamano
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=fabb9a1e1003032236x59a781b8ne0266877db25d001@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitzilla@gmail.com \
--cc=johan@herland.net \
--cc=peff@peff.net \
--cc=pkufranky@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).