git: eb28fee24e - handbook: document new commit message mailing lists

Glen Barber gjb at freebsd.org
Tue Dec 15 06:12:44 UTC 2020


On Mon, Dec 14, 2020 at 10:32:49PM -0700, Warner Losh wrote:
> On Mon, Dec 14, 2020, 10:19 PM Philip Paeps <philip at freebsd.org> wrote:
> 
> > On 2020-12-14 14:06:43 (+0800), Guangyuan Yang wrote:
> > > +      <para><emphasis>Commit message lists:</emphasis> The following
> > > +     lists are for people interested in seeing the log messages for
> > > +     changes to various areas of the source tree.  They are
> > > +     <emphasis>Read-Only</emphasis> lists and should not have mail
> > > +     sent to them.</para>
> >
> > The dev-commits-* lists are not read-only.  All subscribers can post to
> > them.
> >
> 
> I'd love to change things so they are and all follow ups go to a new list,
> maybe dev-commits-discuss....
> 

The only thing I disagree with here is needing to subscribe to a new
list.  Otherwise, I like the idea.

Use case: I intentionally filter ports commit mail out of my inbox
(solely because of the sheer volume of mail), however replies to ports
commits land in by inbox (in order to keep track of whatever post-commit
discussion I need to pay attention to, for example).

I personally do not care about changing a filtering rule to retain the
current behavior, but something to consider for others.

Glen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/dev-commits-doc-all/attachments/20201215/120a18a0/attachment.sig>


More information about the dev-commits-doc-all mailing list