Re: Does Git really need a commit message to go with a commit?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Apr 3, 2010 at 6:06 PM, Ævar Arnfjörð Bjarmason
<avarab@xxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]