Re: Wrap commit messages on `git commit -m`

2012-11-04 Thread Tay Ray Chuan
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

Re: Wrap commit messages on `git commit -m`

2012-11-03 Thread David Aguilar
On Fri, Nov 2, 2012 at 11:38 PM, Jonathan Nieder jrnie...@gmail.com wrote: Ramkumar Ramachandra wrote: Jonathan Nieder wrote: Ram, what platform do your colleagues use? Red Hat Enterprise Linux 5. Oh, ok. In that case I blame habit. I think the best option you have is to just complain

Re: Wrap commit messages on `git commit -m`

2012-11-03 Thread Phil Hord
On Sat, Nov 3, 2012 at 3:41 AM, David Aguilar dav...@gmail.com wrote: On Fri, Nov 2, 2012 at 11:38 PM, Jonathan Nieder jrnie...@gmail.com wrote: Ramkumar Ramachandra wrote: Jonathan Nieder wrote: Ram, what platform do your colleagues use? Red Hat Enterprise Linux 5. Oh, ok. In that case

Re: Wrap commit messages on `git commit -m`

2012-11-02 Thread Ramkumar Ramachandra
Jonathan Nieder wrote: Kevin wrote: As I see it, the problem is not the possibility to add new lines, but colleagues being too lazy to add them. I suspect the underlying problem is that we make it too hard to tell git which text editor to run. Don't we just use $EDITOR? Ram, what

Re: Wrap commit messages on `git commit -m`

2012-11-01 Thread Thomas Adam
Hi, On 1 November 2012 16:07, Ramkumar Ramachandra artag...@gmail.com wrote: 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

Re: Wrap commit messages on `git commit -m`

2012-11-01 Thread James Nylen
On Thu, Nov 1, 2012 at 2:12 PM, Thomas Adam tho...@xteddy.org wrote: Hi, On 1 November 2012 16:07, Ramkumar Ramachandra artag...@gmail.com wrote: 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`.

Re: Wrap commit messages on `git commit -m`

2012-11-01 Thread Lars Gullik Bjønnes
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

Re: Wrap commit messages on `git commit -m`

2012-11-01 Thread Kevin
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 lar...@gullik.org wrote: Ramkumar Ramachandra artag...@gmail.com writes: | Hi, | Some of my colleagues are lazy to fire up an

Re: Wrap commit messages on `git commit -m`

2012-11-01 Thread Jonathan Nieder
Kevin wrote: As I see it, the problem is not the possibility to add new lines, but colleagues being too lazy to add them. I suspect the underlying problem is that we make it too hard to tell git which text editor to run. Ram, what platform do your colleagues use? Thanks, Jonathan -- To