Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 May 2019 09:40:34 -0700 (PDT)
From:      "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>
To:        Pedro Giffuni <pfg@freebsd.org>
Cc:        Doug Moore <unkadoug@gmail.com>, Cy Schubert <Cy.Schubert@cschubert.com>,  Doug Moore <dougm@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   Re: svn commit: r347477 - head/sys/kern
Message-ID:  <201905111640.x4BGeYk0032641@gndrsh.dnsmgr.net>
In-Reply-To: <4dbd3d4b-3d6c-d0b0-e6a7-8c80997124dd@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> Hi;
> 
> On 10/05/2019 23:57, Doug Moore wrote:
> > With mentor approval, I commit r347469.? I start getting email about
> > jenkins failure to build for several architectures on account of the
> > _Generic() construct I introduced in that change.
> >
> > I whip up a patch to undo that part of r347469, and ask for mentor
> > approval.? Meanwhile, mentor authorizes me in email to revert r347469.
> >
> > I try apply applying the fix-patch, and get email that it was rejected
> > for lack of reviewer.? In retrospect, it seems to have been committed
> > anyway as r347472.
> >
> > Thinking that things are still broken, I do what my mentor pre-approved
> > earlier and revert back to before r347469.? A patch to redo r347469,
> > without _Generic(), awaits mentor approval.
> 
> Ugh...? a rather elegant interaction ;)
> 
> > I realize that breaking the build and then committing without mentor
> > approval in my first week as committer isn't a good beginning.?? Sorry
> > about that.
> 
> It's probably not official policy but I would think you don't need 
> mentor approval to revert a change, assuming things return to the 
> pre-commit state, especially if it broke the build.

Perhaps this also should be added to the committers guide of
explaining what and when you need mentor approval, ie I would
consider a revert of a commit that was approved to have
mentor (implicit) type status.

It should also document that mentors can grant mentee's implicit
commit rights, like phk/bde have for all my MFC's, we (I asked,
they granted) agreed that if I had approval to commit it to head
I did not need to ask them for each merge to be approved.  This
one should probably be best a per mentor/mentee type agreement.

> Pedro.
-- 
Rod Grimes                                                 rgrimes@freebsd.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201905111640.x4BGeYk0032641>