This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] limit commit message to 500 lines (was: Please, do not use the merged revisions log as the commit message when merging)
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: "Manuel López-Ibáñez" <lopezibanez at gmail dot com>
- Cc: "Gcc Patch List" <gcc-patches at gcc dot gnu dot org>, "Daniel Berlin" <dberlin at dberlin dot org>
- Date: Tue, 26 Aug 2008 08:06:47 -0700
- Subject: Re: [PATCH] limit commit message to 500 lines (was: Please, do not use the merged revisions log as the commit message when merging)
- References: <6c33472e0808260718v281cff7en1dcc6ec54cdfdcc9@mail.gmail.com>
On Tue, Aug 26, 2008 at 7:18 AM, Manuel López-Ibáñez
<lopezibanez@gmail.com> wrote:
> 2008/8/16 Manuel López-Ibáñez <lopezibanez@gmail.com>:
>> Could we put a limit to the commit log entry? More than 500 hundred
>> lines changelog entries should just be rejected and this will avoid
>> someone accidentally committing a full log or a diff or just random
>> junk.
>>
>
> The following patch to our pre-commit hook enables this. I have tested
> it with a dummy repository but review from bourne-shell and/or
> subversion knowledgeable people would be welcome.
>
When I add 600 testcases, should I mention each of them in commit log?
--
H.J.