From: Bill Davidsen <davidsen@tmr.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Adrian Bunk <bunk@stusta.de>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove BK documentation
Date: Mon, 02 May 2005 12:28:54 -0400 [thread overview]
Message-ID: <42765546.5020600@tmr.com> (raw)
In-Reply-To: <20050501234331.GA9244@havoc.gtf.org>
Jeff Garzik wrote:
> On Mon, May 02, 2005 at 01:34:41AM +0200, Adrian Bunk wrote:
>
>>There's no longer a reason to document the obsolete BK usage.
>>
>>Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
>
> If you are going to remove some documents, please at least have the
> common courtesy of CC'ing the author of the documents.
>
> Speaking as the author of 90% of Documentation/BK-usage directory,
> I ACK this patch.
>
> Jeff
This seems like a good place to thank Adrian for his cleaning fetish,
which makes the kernel code and docs far less confusing, and Jeff, who
put in most of the effort in documenting bk.
Documentation authors really should mention themselves in the
introduction, docs aren't sexy and don't get your name in the news, but
they are a vital part of making Linux usable.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-05-02 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 23:34 [2.6 patch] remove BK documentation Adrian Bunk
2005-05-01 23:43 ` Jeff Garzik
2005-05-02 0:08 ` Adrian Bunk
2005-05-02 0:16 ` Jeff Garzik
2005-05-02 15:53 ` Valdis.Kletnieks
2005-05-02 16:28 ` Bill Davidsen [this message]
2005-05-02 17:06 ` Tommy Reynolds
2005-05-01 23:57 ` Andreas Schwab
2005-05-02 0:04 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-04-09 17:24 Adrian Bunk
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=42765546.5020600@tmr.com \
--to=davidsen@tmr.com \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.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