Quite a few that got to you via Jeff's bk tree were also regular GNU
patches from me. I think the total yesterday was over 200 patches pushed
from me. Who still thinks Linus doesn't scale ? 8-)
> And of those 123 changesets marked as coming from Dave, most were
> obviously written by others, and Dave acted as integrator (which is not
> unimportant, of course - 99% of what I do myself is only integration these
> days).
As a sidenote, I don't mind being attributed in the csets as the source
of where the patch came from, but where I remember/know where the patch
is coming from, I'm making a note in the msg that goes along with it
to the effect of 'Originally from : Joe Hacker'.
> So the statistics get skewed by details like this - if is only a partial
> map of who actually _wrote_ the patch.
If I stuck to a common way of marking the original author, you could
probably enhance your merging scripts to suck that out and attribute
$whoever instead. This only works for patches where I
a. Remember where they came from
b. Are not parts of large "suck everything from latest 2.4.x-pre"
(In most cases, I have no idea who the original author is unless
they were mentioned in the changelog, or I spotted the mail on l-k)
c. I remember to add the magic tag
d. I don't typo the tag/get it wrong.
With Marcelo using bk these days, is it possible that you can cherry
pick certain csets from his bk tree ? If so, it may be that as time
goes on, the need for my forward ports becomes less useful.
Though I'm guessing this would end up more work for you having to
sit clicking around in bk's conflict resolution tool.
Could work well for the simple bits though.
Dave.
-- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/