From: Jeff Garzik <garzik@havoc.gtf.org>
To: Thunder from the hill <thunder@ngforever.de>
Cc: Larry McVoy <lm@bitmover.com>,
Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: Remove Bitkeeper documentation from Linux tree
Date: Mon, 22 Apr 2002 18:38:01 -0400 [thread overview]
Message-ID: <20020422183801.C18907@havoc.gtf.org> (raw)
In-Reply-To: <20020422155223.B20999@havoc.gtf.org> <Pine.LNX.4.44.0204221624300.3714-100000@hawkeye.luckynet.adm>
On Mon, Apr 22, 2002 at 04:31:15PM -0600, Thunder from the hill wrote:
> Hi,
>
> Sorry, I haven't checked email for a while. Putting this into an
> external readme file might still leave some people complaining,
> but if you wish I could do that either.
> The last version was more or less a cut and paste from Larry, this one is
> a little edited...
What I'll do is take this and some of stuff sent to me privately
(spelling correction, peer review stuff) and update that. I will
probably reword your intro here.
A README in that dir might not be a bad idea, but it (like the other
docs) will actually be useful. It will include the "BK disclaimer" as
well as other stuff.
Jeff
next prev parent reply other threads:[~2002-04-22 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 18:37 [PATCH] " Jonathan A. George
2002-04-22 18:58 ` Jeff Garzik
2002-04-22 19:19 ` Jonathan A. George
2002-04-22 19:51 ` Alexander Viro
2002-04-22 19:56 ` Jonathan A. George
2002-04-22 20:13 ` Alexander Viro
2002-04-22 19:52 ` Jeff Garzik
2002-04-22 22:31 ` [PATCH] " Thunder from the hill
2002-04-22 22:38 ` Jeff Garzik [this message]
2002-04-22 21:53 ` [PATCH] " Jonathan A. George
2002-04-22 19:47 ` Anton Altaparmakov
2002-04-22 19:54 ` Jeff Garzik
2002-04-22 21:13 ` Rik van Riel
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=20020422183801.C18907@havoc.gtf.org \
--to=garzik@havoc.gtf.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=thunder@ngforever.de \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®