From: Dave Jones <davej@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Larry McVoy <lm@bitmover.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.5.8-pre1
Date: Thu, 4 Apr 2002 22:34:25 +0200 [thread overview]
Message-ID: <20020404223425.K11833@suse.de> (raw)
In-Reply-To: <20020403195445.U17549@work.bitmover.com> <Pine.LNX.4.33.0204041203440.14206-100000@penguin.transmeta.com>
On Thu, Apr 04, 2002 at 12:12:07PM -0800, Linus Torvalds wrote:
> Anyway: of the 147 patches, 125 were merges from Dave Jones (only 123 are
> marged as such - two were re-attributed by me by hand by editing the
> emails directly).
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
next prev parent reply other threads:[~2002-04-04 20:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 1:22 Linux-2.5.8-pre1 Linus Torvalds
2002-04-04 3:46 ` Linux-2.5.8-pre1 Larry McVoy
2002-04-04 3:54 ` Linux-2.5.8-pre1 Larry McVoy
2002-04-04 20:12 ` Linux-2.5.8-pre1 Linus Torvalds
2002-04-04 20:18 ` Linux-2.5.8-pre1 Larry McVoy
2002-04-04 20:34 ` Dave Jones [this message]
2002-04-06 15:36 ` Linux-2.5.8-pre1 David Woodhouse
2002-04-06 17:05 ` Linux-2.5.8-pre1 Larry McVoy
2002-04-06 17:25 ` Linux-2.5.8-pre1 David Woodhouse
2002-04-06 17:30 ` Linux-2.5.8-pre1 Larry McVoy
2002-04-06 19:14 ` Linux-2.5.8-pre1 David Woodhouse
2002-04-04 10:19 ` Linux-2.5.8-pre1 Martin Dalecki
2002-04-04 11:45 ` Linux-2.5.8-pre1 Tim Schmielau
2002-04-04 10:49 ` Linux-2.5.8-pre1 Martin Dalecki
2002-04-05 6:02 ` [patch] Linux-2.5.8-pre1 Tim Schmielau
2002-04-04 12:05 ` Linux-2.5.8-pre1 Dave Jones
2002-04-04 15:45 ` IDE/SUPPORT_VLB_SYNC in 2.5.x Geert Uytterhoeven
2002-04-04 14:52 ` Martin Dalecki
2002-04-05 8:26 ` Geert Uytterhoeven
2002-04-04 11:55 ` Linux-2.5.8-pre1 fs/dquot Martin Dalecki
2002-04-04 16:43 ` Alexander Viro
2002-04-04 15:50 ` Martin Dalecki
2002-04-04 22:52 ` Linux-2.5.8-pre1 Mike Fedyk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020404223425.K11833@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox