From: Bruce Ferrell <bferrell@baywinds.org>
To: john slee <indigoid@higherplane.net>
Cc: Shlomi Fish <shlomif@vipe.stud.technion.ac.il>,
linux-kernel@vger.kernel.org
Subject: Re: An Analysis of BitKeeper and BitMover's Strategy
Date: Sun, 10 Nov 2002 09:08:46 -0800 [thread overview]
Message-ID: <3DCE929E.6010307@baywinds.org> (raw)
In-Reply-To: 20021110004847.GB17478@higherplane.net
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
While the posting wasn't directly linked to kernel development, I did
find the analysis to be thought provoking. I think calling it spam
MIGHT be too strong.
john slee wrote:
> On Sat, Nov 09, 2002 at 12:18:24PM +0200, Shlomi Fish wrote:
>
>>As part of the "Better SCM" site (that is still under construction), I
>>wrote a few essays about BitKeeper:
>
>
> please do not spam the list with this crap
>
> j.
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3257 bytes --]
prev parent reply other threads:[~2002-11-10 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 10:18 An Analysis of BitKeeper and BitMover's Strategy Shlomi Fish
2002-11-10 0:48 ` john slee
2002-11-10 17:08 ` Bruce Ferrell [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=3DCE929E.6010307@baywinds.org \
--to=bferrell@baywinds.org \
--cc=indigoid@higherplane.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shlomif@vipe.stud.technion.ac.il \
/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