Re: git: 6b96125afdf2 - main - cap_net.3: remove a copypasta

On Wed, Dec 6, 2023, 8:59 PM Alan Somers <asomers@freebsd.org> wrote:

> On Wed, Dec 6, 2023 at 6:55 PM Zhenlei Huang <zlei@freebsd.org> wrote:
> >
> >
> >
> > > On Dec 7, 2023, at 12:52 AM, Alan Somers <asomers@freebsd.org> wrote:
> > >
> > > The branch main has been updated by asomers:
> > >
> > > URL:
> https://cgit.FreeBSD.org/src/commit/?id=6b96125afdf245ae61dd82b59891ad0d6aab0066
> > >
> > > commit 6b96125afdf245ae61dd82b59891ad0d6aab0066
> > > Author:     Alan Somers <asomers@FreeBSD.org>
> > > AuthorDate: 2023-12-05 23:23:29 +0000
> > > Commit:     Alan Somers <asomers@FreeBSD.org>
> > > CommitDate: 2023-12-06 16:51:37 +0000
> > >
> > >    cap_net.3: remove a copypasta
> > >
> > >    This line appears to have been copied from cap_sysctl.3.  While I'm
> > >    here, reorder and reword the description of cap_net_limit a bit.
> > >
> > >    [skip ci]
> >
> > I guess we can 'skip ci' implicitly for document or typo changes.
>
> Can we?   The skipping logic is builtin to Jenkins, Github Workflows,
> and Cirrus.  I don't think it would be easy to program any of those to
> detect which changes can be safely skipped.
>

The message currently is a nearly nop for our setup. Jenkins runs arent
triggered by a commit. Cirrus CI already can't maje it more than a few days
into the month. Commits aren't gated into main by CI. So IMHO, it just adds
noise. Let's drop it until it has an actual beneficial effect. Metadata
like that doesn't really belong in the git log.

As this situation changes, we can reevaluate...

Again just my opinion...

Warner

-Alan
>