From: Adrian Bunk <bunk@fs.tum.de>
To: "John A. Martin" <jam@athene.jamux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] John A. Martin no longer maintains the CREDITS file
Date: Fri, 28 May 2004 00:29:39 +0200 [thread overview]
Message-ID: <20040527222938.GY16099@fs.tum.de> (raw)
In-Reply-To: <87y8nf5l8e.fsf@athene.jamux.com>
On Wed, May 26, 2004 at 10:14:25AM -0400, John A. Martin wrote:
> >>>>> "Adrian" == Adrian Bunk
> >>>>> "[patch] John A. Martin no longer maintains the CREDITS file"
> >>>>> Mon, 24 May 2004 02:01:07 +0200
>
> Adrian> This information seems to be quite outdated.
> Adrian> cu
> Adrian> Adrian
>
> I cannot remember the last time I've seen a request for CREDITS file
> maintenance. The frequency of requests seemed to drop off sharply at
> some point several years ago, perhaps when access to CVS was
> broadened, IIRC.
>
> I'd be more than happy to continue/resume maintenance of the CREDITS
> file if that is wanted.
>...
> I have not been reading linux-kernel mail regularly for a while but
> I'm looking at gmane.linux.kernel now and sending this followup that
> way.
>
> Please let me know if my help with the CREDITS file is still wanted.
The CREDITS file changes usually come from the people listed, and new
people are most often added as part of the patch that adds the code
they've written.
Your work in the past is appreciated, but effectively Linus and Andrew
maintain the CREDITS file today.
> jam
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2004-05-27 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 0:01 [patch] John A. Martin no longer maintains the CREDITS file Adrian Bunk
2004-05-26 14:14 ` John A. Martin
2004-05-27 22:29 ` Adrian Bunk [this message]
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=20040527222938.GY16099@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=jam@athene.jamux.com \
--cc=linux-kernel@vger.kernel.org \
/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