> To: ALFS Discussion and Development List > <[email protected]> > From: Bruce Dubbs <[email protected]> > Date: Tue, 4 Apr 2017 10:49:38 -0500 > Subject: Re: [alfs] '[...]' labels on subject line for *alfs lists. > > Pierre Labastie wrote: > > On 04/04/2017 11:20, Pierre Labastie wrote: > >> On 04/04/2017 10:27, akhiezer wrote: > >>> Hi, > >>> > >>> Could the *alfs lists use '[...]' labels on subject lines - like what > >>> lfs/blfs/clfs book/dev/support/trac/&c do - e.g.: > >>> == > >>> * LFS Trac Fri Mar 31 20:23 [lfs-book] [LFS Trac] Batch > >>> modify: #4069, #4070 > >>> * LFS Trac Tue Apr 4 02:46 Re: [lfs-book] [LFS Trac] #4071: > >>> bc-1.07 > >>> * via blfs-book Sat Apr 1 15:39 [blfs-book] r18542 - in > >>> trunk/BOOK: . introduction/welcome networking/netprogs > >>> * [email protected] Sun Mar 19 22:15 [website] r1394 - html/trunk/alfs > >>> * git Sun Apr 2 21:21 [Clfs-commits] > >>> [Cross-LFS]Cross-LFS Book branch, master, updated. > >>> clfs-3.0.0-systemd-274-g13de3e1 > >>> == > >>> > >> Good question. It would make filtering easier. ATM, I use the "to" > >> field, which always contains "alfs-{log,discuss,...}", but it is > >> suboptimal... I guess Bruce would know what to do better than I would, > >> but let me look at that. > > Should be fixed. >
There's two lists: [email protected] [email protected] It'd be clearer/better to have per-list labels - e.g. (as a first approx): [alfs-discuss] [alfs-log] The '[alfs-log]' is approx equiv to lfs-book/blfs-book: and the latter are finer-grained into: [lfs-book] [LFS Trac] [lfs-book] [blfs-book] [BLFS Trac] [blfs-book] So overall for *alfs the equiv would/could/may be: [alfs-discuss] [alfs-log] [ALFS Trac] [alfs-log] rgds, akh -- -- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
