public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.5.8-pre1
Date: Thu, 4 Apr 2002 12:18:48 -0800	[thread overview]
Message-ID: <20020404121848.H17549@work.bitmover.com> (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:
> > You can click on any name to see what they have been working on, once you
> > drill down through a name, you are looking at things through a "this user
> > only" filter.
> 
> Side note: this only works partially.
> 
> For example, of the 297 changesets in 2.5.8-pre1, 147 were from email
> patches (the 50% ratio seems to have held up pretty well over time:  
> about half of the submissions I get are old-style patches, with half being
> BK merges. Of course, for me the advantage of BK is that the BK merge half
> often required _much_ less than 50% of the time).

OK, I think I see.  If you get a GNU patch from someone like Dave who got
it from someone else, then it shows up as Dave in your changelogs.  Hmm.
Do you think it is worthwhile to try and do some parsing of the message
such that we can set $BK_USER to the right person if the message contains
the info?  Dave is pretty good about doing stuff like 

	Patch description...
	Originally from Matt Domsch.

If we formalized that a bit we could get the annotations right.  I know
it may sound like an ego stroking exercise, but it's actually very useful
when looking at the annotated history to see who did something, it makes
it easier to track them down and feed them new changes/suggestions/etc.
Yeah, it makes it easier to bug them with questions too, but that tends
to happen anyway.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-04-04 20:19 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       ` Larry McVoy [this message]
2002-04-04 20:34       ` Linux-2.5.8-pre1 Dave Jones
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=20020404121848.H17549@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=linux-kernel@vger.kernel.org \
    --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