> Date: Sun, 16 Apr 2017 17:07:33 -0500 > From: William Harrington <kb0...@berzerkula.org> > To: clfs-...@lists.clfs.org > Subject: Re: [Clfs-dev] [Clfs-support] better info on subject-line of > git-hook mails. > > On Sun, 16 Apr 2017 12:00:50 +0100 > lf...@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 > > > > > > > > > > > > -- >
Your answer exemplifies the slightly parlous stop-start, no-releases, states of the various clfs projects, sites down & unnoticed, domains expiring & unnoticed, &c. Improve. > CLFS-Commits is for trac and commit traffic. Therefore it is reasonable to have sent to 'clfs-support@...' . > There is no reason someone should be commenting on clfs-commits in > clfs-support. - confidently wrong as so often. See above. > Anyone can subscribe to the clfs-commits mailing list, but it isn't useful > information for anyone wanting to build CLFS. That latter part is nonsense; and lacking in scope of vision. > The important information is in the rendered book, which is of importance to > CLFS users. It's not the only important information. Besides, the books are littered with errors; and so are missing important information; and so it is false to say that 'the important information is in the rendered book'; ref above re parlous state. > > Also, the commit subject is valid, and the e-mail body describes the > change(s). Bad presentation of information: folks should be able to see the summary in mail-folder index-list summary. But if you don't even understand that without needing it explained, ... ref again parlous state. > > There is no more or less info required on the subject line other than a > commit was made. - completely wrong-headed, and failing to grasp basics: ref above re visible in index-list subject-lines. > This should be brought up in the clfs-dev mailing list. It has no use here. > Again, that is false; ref above re reasonable to have sent to ...support@... . > Is there any dev input on this? Ref again 'parlous state': do bear in mind that new inputs from 'new' sources, might actually help to _improve_ the situation; rather than be stuck with 'same-old, same-old' dysfunctional loop that could do with being broken out of. akh -- _______________________________________________ Clfs-support mailing list Clfs-support@lists.clfs.org http://lists.clfs.org/listinfo.cgi/clfs-support-clfs.org
