From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758294AbWLIVlo (ORCPT ); Sat, 9 Dec 2006 16:41:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758281AbWLIVlo (ORCPT ); Sat, 9 Dec 2006 16:41:44 -0500 Received: from einhorn.in-berlin.de ([192.109.42.8]:60129 "EHLO einhorn.in-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758161AbWLIVln (ORCPT ); Sat, 9 Dec 2006 16:41:43 -0500 X-Envelope-From: stefanr@s5r6.in-berlin.de Message-ID: <457B2D67.2050202@s5r6.in-berlin.de> Date: Sat, 09 Dec 2006 22:40:55 +0100 From: Stefan Richter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061202 SeaMonkey/1.0.6 MIME-Version: 1.0 To: "Robert P. J. Day" CC: Jeff Garzik , Linux kernel mailing list Subject: Re: why are some of my patches being credited to other "authors"? References: <457A9F3B.6020009@garzik.org> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Robert P. J. Day wrote: > i'm far more interested in at least knowing what happens to patches > once they enter the system, so i can plan on what kind of cleanup i > can work on next. The maintainers handle this differently. If you don't get feedback nor see your patch appearing in the maintainer's repo after a while, just ask what happened or repost your patch (with a [resend] flag or a respective note below the patch description). -- Stefan Richter -=====-=-==- ==-- -=--= http://arcgraph.de/sr/