From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: Paul Jackson <pj@sgi.com>
Cc: git@vger.kernel.org
Subject: Re: Yet another base64 patch
Date: Sun, 17 Apr 2005 13:51:52 -0400 [thread overview]
Message-ID: <4262A238.3050207@dwheeler.com> (raw)
In-Reply-To: <20050417011615.3e7dfb29.pj@sgi.com>
Paul Jackson wrote:
> David wrote:
>
>>My list would be:
>>ext2, ext3, NFS, and Windows' NTFS (stupid short filenames,
>>case-insensitive/case-preserving).
>
>
> I'm no mind reader, but I'd bet a pretty penny that what you have in
> mind and what Linus has in mind have no overlaps in their solution sets.
Sadly, I lack the mind reading ability as well.
Our goals are, I suspect, somewhat different.
Linus wants to build a tool that meets his specific needs
(managing kernel development), and he has particular requirements
(such as fast simple merging when working at large scales).
In contrast, I'm hoping for a more
general OSS/FS SCM tool that many others can use as well.
But I think there's heavy overlap in the solution space.
The Linux kernel project is, to my knowledge, the largest
project using a truly distributed SCM process.
Anyone else who is considering a distributed SCM process
would at _least_ want to think about how the Linux kernel
project works, and if they're doing so, they
might also want to reuse the development tools.
I'm just taking a peek, and
looking for situations where a design decision is irrelevant
for his purposes, but a particular direction would be of
particular help to other projects. I'm more worried about the
storage format; if the code doesn't support some particular
feature but it could be added later without great pain, no big deal.
If something would imply a complete rewrite, that's undesirable.
--- David A. Wheeler
next prev parent reply other threads:[~2005-04-17 17:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 4:19 Yet another base64 patch H. Peter Anvin
2005-04-14 2:24 ` Christopher Li
2005-04-14 5:36 ` H. Peter Anvin
2005-04-14 2:42 ` Christopher Li
2005-04-14 6:27 ` H. Peter Anvin
2005-04-14 6:35 ` H. Peter Anvin
2005-04-14 7:40 ` Linus Torvalds
2005-04-14 16:58 ` H. Peter Anvin
2005-04-14 17:42 ` Linus Torvalds
2005-04-14 19:11 ` bert hubert
2005-04-14 19:25 ` H. Peter Anvin
2005-04-14 21:47 ` bert hubert
2005-04-15 0:44 ` Linus Torvalds
2005-04-15 1:06 ` H. Peter Anvin
2005-04-17 4:10 ` David Lang
2005-04-18 6:23 ` H. Peter Anvin
2005-04-15 1:07 ` H. Peter Anvin
2005-04-15 3:58 ` Paul Jackson
2005-04-17 3:53 ` David A. Wheeler
2005-04-17 4:05 ` Paul Jackson
2005-04-17 6:38 ` David A. Wheeler
2005-04-17 8:16 ` Paul Jackson
2005-04-17 17:51 ` David A. Wheeler [this message]
2005-04-17 18:19 ` Petr Baudis
2005-04-18 5:13 ` David A. Wheeler
2005-04-18 12:59 ` Kevin Smith
2005-04-18 16:42 ` David A. Wheeler
2005-04-17 14:30 ` Daniel Barkalow
2005-04-17 16:29 ` David A. Wheeler
2005-04-14 4:25 ` H. Peter Anvin
2005-04-14 8:17 ` Linus Torvalds
2005-04-14 17:02 ` H. Peter Anvin
2005-04-15 23:55 ` Paul Dickson
2005-04-18 6:28 ` H. Peter Anvin
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=4262A238.3050207@dwheeler.com \
--to=dwheeler@dwheeler.com \
--cc=git@vger.kernel.org \
--cc=pj@sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).