From: Mike Taht <mike.taht@timesys.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: David Roundy <droundy@abridgegame.org>,
git@vger.kernel.org, darcs-devel@darcs.net
Subject: Re: using git directory cache code in darcs?
Date: Sun, 17 Apr 2005 09:49:18 -0700 [thread overview]
Message-ID: <4262938E.8010107@timesys.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504170916080.7211@ppc970.osdl.org>
Linus Torvalds wrote:
>
> On Sun, 17 Apr 2005, David Roundy wrote:
>
>>That's all right. Darcs would only access the cached data through a
>>git-caching layer, and we've already got an abstraction layer over the
>>pristine cache. As long as the git layer can quickly retrieve the contents
>>of a given file, we should be fine.
>
>
> Yes.
>
> In fact, one of my hopes was that other SCM's could just use the git
> plumbing. But then I'd really suggest that you use "git" itself, not any
> "libgit". Ie you take _all_ the plumbing as real programs, and instead of
> trying to link against individual routines, you'd _script_ it.
If you don't want it, I won't do it. Still makes sense to separate the
plumbing from the porcelain, though.
--
Mike Taht
"You can tell how far we have to go, when FORTRAN is the language of
supercomputers.
-- Steven Feiner"
next prev parent reply other threads:[~2005-04-17 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 13:22 using git directory cache code in darcs? David Roundy
2005-04-16 13:31 ` Ingo Molnar
2005-04-16 14:28 ` Junio C Hamano
2005-04-16 22:43 ` Linus Torvalds
2005-04-17 12:17 ` David Roundy
2005-04-17 16:24 ` Linus Torvalds
2005-04-17 16:49 ` Mike Taht [this message]
2005-04-17 22:37 ` Nomad Arton
2005-04-17 23:23 ` Junio C Hamano
2005-04-18 2:00 ` Paul Jackson
2005-04-18 2:56 ` Paul Jackson
2005-04-18 3:06 ` Linus Torvalds
2005-04-18 4:36 ` Paul Jackson
2005-04-18 9:23 ` git options Mike Taht
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=4262938E.8010107@timesys.com \
--to=mike.taht@timesys.com \
--cc=darcs-devel@darcs.net \
--cc=droundy@abridgegame.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).