[Clfs-dev] [Clfs-support] better info on subject-line of git-hook mails.

[William Harrington]

On Sun, 16 Apr 2017 12:00:50 +0100
lfs65 at cruziero.com (akhiezer) wrote:

> 
> 
> Currently 'subject' lines are of the form:
> --
> Subject: [Clfs-commits] [Cross-LFS]Cross-LFS Book branch, sysvinit, updated. clfs-3.0.0-sysvinit-276-g1b6e9c5
> --
> 
> 
> It would be useful if it included some indication of the content of
> the commit - e.g.:
> ==
> Update KBD to 2.0.4 .
> ==
> 
> 
> To accommodate that, the '[Cross-LFS]Cross-LFS' string could be
> abbreviated to e.g. '[CLFS] CLFS' .
> 
> 
> And the 'subject' line might then be of the format:
> --
> Subject: [Clfs-commits] [CLFS] Book branch, sysvinit, updated. 'Update KBD to 2.0.4' . clfs-3.0.0-sysvinit-276-g1b6e9c5
> --
> 
> 
> The 'Update KBD to 2.0.4' string would be auto-extracted from the
> git-commit message: and would be restricted to a max-length, with
> truncation indicated by '...' or similar.
> 
> 
> 
> akh
> 
> 
> 
> 
> 
> --

CLFS-Commits is for trac and commit traffic. There is no reason someone should be commenting on clfs-commits in clfs-support. Anyone can subscribe to the clfs-commits mailing list, but it isn't useful information for anyone wanting to build CLFS. The important information is in the rendered book, which is of importance to CLFS users.

Also, the commit subject is valid, and the e-mail body describes the change(s).

There is no more or less info required on the subject line other than a commit was made. This should be brought up in the clfs-dev mailing list. It has no use here.

Is there any dev input on this?

Sincerely,

William Harrington