Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 May 2018 19:31:40 -0400
From:      "Jonathan T. Looney" <jtl@freebsd.org>
To:        Stephen Hurd <shurd@freebsd.org>
Cc:        src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org,  svn-src-stable@freebsd.org, svn-src-stable-11@freebsd.org
Subject:   Re: svn commit: r333503 - stable/11/sys/net
Message-ID:  <CADrOrmuKJvUh7C_Y=KtG9WBtsQvaQHJ7=CFYjtvPKbrc=r1GMg@mail.gmail.com>
In-Reply-To: <201805112040.w4BKeQvO053076@repo.freebsd.org>
References:  <201805112040.w4BKeQvO053076@repo.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 11, 2018 at 4:40 PM, Stephen Hurd <shurd@freebsd.org> wrote:
>
> Author: shurd
> Date: Fri May 11 20:40:26 2018
> New Revision: 333503
> URL: https://svnweb.freebsd.org/changeset/base/333503
>
> Log:
>   MFC r333329, r333366, r333373
>
>   r333329: Fix off-by-one error requesting tx interrupt
>   r333366: Cleanup queues when iflib_device_register fails
>   r333373: Log iflib_tx_structures_setup failure in function
>

Is this an acceptable style for MFC logs?

I'm asking because I actually prefer this to reading (or compiling) the
concatenated log messages from several changes. However, I never knew it
was acceptable to summarize like this. If it is, I'd like to know so I can
adopt it for run-of-the-mill MFCs.

Jonathan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADrOrmuKJvUh7C_Y=KtG9WBtsQvaQHJ7=CFYjtvPKbrc=r1GMg>