Re: Wrap commit messages on `git commit -m`
- From
Kevin <ikke@ikke.info>
- Date
- Nov 1, 2012, 21:52 UTC
- Message-ID
- <CAO54GHDRBDyQYvo-g_xEvsQJRgtfbbT-4-kop8hoSK1D37G44w@mail.gmail.com>
- In-Reply-To
- <m3a9v170ca.fsf@black.gullik.net>
As I see it, the problem is not the possibility to add new lines, but colleagues being too lazy to add them.
On Thu, Nov 1, 2012 at 5:29 PM, Lars Gullik Bjønnes <larsbj@gullik.org> wrote:
Show 28 quoted lines
> Ramkumar Ramachandra <artagnon@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. > > -- > Lgb > > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html