From: Avery Pennarun <apenwarr@gmail.com>
Date: Sun, 04 Apr 2010 01:58:23 GMT
Subject: Re: Does Git really need a commit message to go with a commit?
Message-ID: <w2v32541b131004031858t692577a7p5009637f831bff46@mail.gmail.com>
In-Reply-To: <z2r51dd1af81004031506pc9ac1840ie9953ae6df91d01b@mail.gmail.com>

On Sat, Apr 3, 2010 at 6:06 PM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> git-commit(1) doesn't allow you to make a commit without a commit
> message. This is annoying and doesn't properly preserve history in
> applications like snerp-vortex which replay a SVN dump into Git. You
> have to add `$msg = "Git made me do it" unless length $msg' somewhere.
>
> Is there really no way to add a commit with no message with the git
> tools? Will anything break if I manually construct a commit with no
> message? Are commit messages inherently part of the format or does
> git-commit(1) just think it knows better than me?

git-commit isn't really meant to be used by scripts.  Try using
git-commit-tree instead, which doesn't enforce a commit message.

(Or use git fast-import; a quick glance at Snerp suggests that it's
intended to be *fast*; using fast-import ought to make things vastly
quicker.)

Avery