[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] 72 chars for git log messages [Was: Improved input-sequence ed
|
From: |
Greg Chicares |
|
Subject: |
Re: [lmi] 72 chars for git log messages [Was: Improved input-sequence editor] |
|
Date: |
Sun, 29 May 2016 16:00:16 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.8.0 |
On 2016-05-29 13:22, Greg Chicares wrote:
> On 2016-05-28 18:16, Vadim Zeitlin wrote:
[...quickly agreeing for once...]
> so I'm satisfied if we agree never to write any line longer than seventy-two
> characters anywhere.
BTW, I'm going to add a number in square brackets to the first line of
any commit message that changes the defect count that 'test_coding_rules'
reports.
- [lmi] Improved input-sequence editor, Greg Chicares, 2016/05/12
- Re: [lmi] Improved input-sequence editor, Greg Chicares, 2016/05/12
- Re: [lmi] Improved input-sequence editor, Greg Chicares, 2016/05/27
- Re: [lmi] Improved input-sequence editor, Vadim Zeitlin, 2016/05/28
- [lmi] 72 chars for git log messages [Was: Improved input-sequence editor], Greg Chicares, 2016/05/29
- Re: [lmi] 72 chars for git log messages [Was: Improved input-sequence editor],
Greg Chicares <=
- Re: [lmi] 72 chars for git log messages [Was: Improved input-sequence editor], Vadim Zeitlin, 2016/05/29
- Re: [lmi] 72 chars for git log messages [Was: Improved input-sequence editor], Greg Chicares, 2016/05/30
- Re: [lmi] 72 chars for git log messages, Vadim Zeitlin, 2016/05/30
- Re: [lmi] 72 chars for git log messages, Greg Chicares, 2016/05/31
Re: [lmi] Improved input-sequence editor, Greg Chicares, 2016/05/28