svn commit: r330972 - stable/11/share/misc

[Warner Losh]

On Thu, Mar 15, 2018 at 10:20 AM, Ian Lepore <ian at freebsd.org> wrote:

> On Thu, 2018-03-15 at 09:14 -0700, Rodney W. Grimes wrote:
> > >
> > > On Thu, 2018-03-15 at 10:52 -0500, Justin Hibbits wrote:
> > > >
> > > > On Thu, Mar 15, 2018 at 10:46 AM, Ian Lepore <ian at freebsd.org>
> > > > wrote:
> > > > >
> > > > >
> > > > > I agree completely with all of this.??It bothers me how many
> > > > > committers
> > > > > have the attitude that handling MFCs is not part of being a
> > > > > committer.
> > > > Never attribute to arrogance that which can adequately be
> > > > explained
> > > > by
> > > > sheer laziness ;)
> > > >
> > > > - Justin (guilty of marking changes as MFC after, and ignoring
> > > > them
> > > > for far too long)
> > > >
> > > Laziness and procrastination I understand -- I own a lovely glass
> > > house
> > > in that neighborhood. ?I tend to put off MFCs for way too long then
> > > every few months have to spend a whole weekend catching up.
> > MFC: 1 week (by pool|self)    #defaults to self if missing
> >
> > There is already a very nice tracking tool for outstanding MFC's,
> > if we added a bit of smarts in its parser, and created a pool of
> > MFC commiters (Eitan seems to have started one :-)) those who
> > do not want to do there own MFC work could pass the hat.
>
> If you're talking about the MFC after: field in commits, I don't use
> it. I have about zero tolerance for being nagged by anybody about
> anything, and that goes double for robots nagging me with spam mail.
>
> The MFC tool that works well for me is gonzo's MFCTracker site [*] that
> doesn't require extra markup in the commit messages.
>

I also have a MFC tool for git, but it's n