On Wed, 2013-09-11 at 09:24 +0200, Stefano Babic wrote: > Hi Scott, > > On 10/09/2013 22:11, Scott Wood wrote: > > Sure. > > > > Acked-by: Scott Wood <scottw...@freescale.com> > > > > I'm curious who's been doing these patchwork assignments and what > > they're basing it on. > > > > I think that everyone of us custodians has write rights to assign > patches. Personally, I check the list and I assign myself the i.MXes. > Surely there are a lot of unassigned patches, and someone tries to make > order - better there is who takes care of a patch as to let the patch > oblivious.
Sure... Probably what prompted the comment more than this was when other people assign patches to me that aren't in the NAND code (e.g. UBI patches, or patches in arch/board code). Then I need to choose between just unassigning them, or figuring out who to assign them to, and I can't even see who assigned them to me to ask them about it. A log of patchwork updates would be nice. > However, this is an error-prone approach, and it should be > nice if there could be an automatic way to assign patches, maybe using > the subject. It'd be nice if the files touched could be used. -Scott _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
