On Thu, Nov 1, 2012 at 11:29 AM, Lars Gullik Bjønnes <lar...@gullik.org> wrote:
> Ramkumar Ramachandra <artag...@gmail.com> writes:
> | Hi,
> | Some of my colleagues are lazy to fire up an editor and write proper
> | commit messages- they often write one-liners using `git commit -m`.
> | However, that line turns out to be longer than 72 characters, and the
> | resulting `git log` output is ugly.  So, I was wondering if it would
> | be a good idea to wrap these one-liners to 72 characters
> | automatically.
> git commit -m 'foo: fix this problem
> This problem is fixed by doing foo,
> bar and baz.
> Signed-off-by: me
> '
> works.

Perhaps a deeper issue is that the implicit email format
(subject-body) for commit messages, is, well, implicit. New users of
git who type git-commit -m '...' isn't going to know that those few
characters will all be lumped on a "subject" line, forever screwing
themselves when they review the output of git-log, git-rebase
--interactive, etc. (can't remember off the top of my head if
git-format-patch would chop off long subjects and move it to the
body), which may be a significant period of time (and thus commits)

While I don't have any ideas on how to improve on this, hopefully this
gets recognized as an issue in the first place.

Ray Chuan
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to