* gcc git hook
@ 2020-09-10 12:48 Nathan Sidwell
2020-09-10 17:21 ` Joseph Myers
0 siblings, 1 reply; 3+ messages in thread
From: Nathan Sidwell @ 2020-09-10 12:48 UTC (permalink / raw)
To: Martin Liška, Joseph Myers; +Cc: GCC Patches
Is it possible for the git hooks to reject pushes with overly-long
subject lines?
I occasionally see pushes that forgot to add a separate title line, and
so the whole of the commit description gets used.
nathan
--
Nathan Sidwell
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: gcc git hook
2020-09-10 12:48 gcc git hook Nathan Sidwell
@ 2020-09-10 17:21 ` Joseph Myers
2020-09-10 17:29 ` Nathan Sidwell
0 siblings, 1 reply; 3+ messages in thread
From: Joseph Myers @ 2020-09-10 17:21 UTC (permalink / raw)
To: Nathan Sidwell; +Cc: Martin Liška, GCC Patches
On Thu, 10 Sep 2020, Nathan Sidwell wrote:
> Is it possible for the git hooks to reject pushes with overly-long subject
> lines?
>
> I occasionally see pushes that forgot to add a separate title line, and so the
> whole of the commit description gets used.
Is that where the whole description is a single long unwrapped line?
(The case of no blank line after the first line - a message starting with
a multi-line paragraph - should already be diagnosed.)
We've disabled the check on lengths of lines in commit messages:
# We do not want to force a maximum line length in commit
# revision logs, as they get in the way of copy-pasting
# debugging session, error messages, logs, etc.
max-rh-line-length = 0
But we could add a local check in our commit_checker script for just the
length of the first line (alongside the checks for a first line that looks
like a ChangeLog header or is just a single word).
--
Joseph S. Myers
joseph@codesourcery.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: gcc git hook
2020-09-10 17:21 ` Joseph Myers
@ 2020-09-10 17:29 ` Nathan Sidwell
0 siblings, 0 replies; 3+ messages in thread
From: Nathan Sidwell @ 2020-09-10 17:29 UTC (permalink / raw)
To: Joseph Myers; +Cc: Martin Liška, GCC Patches
On 9/10/20 1:21 PM, Joseph Myers wrote:
> On Thu, 10 Sep 2020, Nathan Sidwell wrote:
>
>> Is it possible for the git hooks to reject pushes with overly-long subject
>> lines?
>>
>> I occasionally see pushes that forgot to add a separate title line, and so the
>> whole of the commit description gets used.
>
> Is that where the whole description is a single long unwrapped line?
> (The case of no blank line after the first line - a message starting with
> a multi-line paragraph - should already be diagnosed.)
the most recent is ad2a37157d3, where it is indeed as you say. I know
I've done it in too.
>
> We've disabled the check on lengths of lines in commit messages:
>
> # We do not want to force a maximum line length in commit
> # revision logs, as they get in the way of copy-pasting
> # debugging session, error messages, logs, etc.
> max-rh-line-length = 0
>
> But we could add a local check in our commit_checker script for just the
> length of the first line (alongside the checks for a first line that looks
> like a ChangeLog header or is just a single word).
>
--
Nathan Sidwell
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-09-10 17:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-10 12:48 gcc git hook Nathan Sidwell
2020-09-10 17:21 ` Joseph Myers
2020-09-10 17:29 ` Nathan Sidwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).