[DIM PATCH 1/2] TODO: Cc patch authors when tagging and generating PRs

[Sean Paul]

On Thu, Mar 22, 2018 at 03:26:01PM +0200, Jani Nikula wrote:
> On Thu, 22 Mar 2018, Sean Paul <seanpaul at chromium.org> wrote:
> > Yeah, my apologies for jumping the gun, I had assumed TODO was more wiki style
> > than the rest of the tree. I'll make sure it bakes on list next time.
> 
> I guess it is a bit wiki style... I just don't want us to set a bad
> example now that we have such a large pool of folks with push access to
> maintainer-tools.
> 
> > -misc-next is at least the same. It'll be easier for my workflow since I won't
> > need to manually copy/paste the entries over from gitk to the tag, but I
> > certainly can't speak for others. I was thinking this could be hidden behind a
> > DIM_TEMPLATE flag for those who want it.
> 
> I hadn't even realized it was part of your workflow. Do you do that
> regularly now for drm-misc-*?

Yep, I've been doing this for a while now.


> Are people happy with that?

I do it for myself more than anyone else. I Cc everyone who gets a line item in
my tag so they can fact check my summary and correct me if I get it wrong. So, I
guess I'm happy with it :).

If the Cc was harvested automatically, I would just trim out those people who
aren't in the summary so they aren't spammed. The list might get a bit crazy for
the first -misc-next PR in a release cycle, but other than that it'd probably be
a net-win.

Sean

> 
> > Again, I'm sorry for the direct push, won't happen again.
> 
> Hey, don't worry about it.
> 
> BR,
> Jani.
> 
> 
> -- 
> Jani Nikula, Intel Open Source Technology Center

-- 
Sean Paul, Software Engineer, Google / Chromium OS