From: Junio C Hamano <junkio@cox.net>
To: Frank Sorenson <frank@tuxrocks.com>
Cc: Catalin Marinas <catalin.marinas@gmail.com>,
Bryan Larsen <bryan.larsen@gmail.com>,
git@vger.kernel.org
Subject: Re: Barebone Porcelain. Where to stop?
Date: Mon, 18 Jul 2005 17:10:36 -0700 [thread overview]
Message-ID: <7vy883lkoz.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 42DC17C5.80000@tuxrocks.com
Frank Sorenson <frank@tuxrocks.com> writes:
> Is this something we want to consider, or am I out in left field? :)
I do not think so. You just more clearly and explicitly stated
what I wanted to see; we share the same vision of the ideal
world.
I do however think your sights are probably focused at somewhere
a lot further then mine ;-). C level interfaces to those
aggregated common operations would happen once after we identify
what kind of common operations are useful to have, prototyping
them (most likely in scripting environment), and if it turns out
to be useful and performance critical. I personally do not
think we are there yet.
prev parent reply other threads:[~2005-07-19 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 17:37 Barebone Porcelain. Where to stop? Junio C Hamano
2005-07-18 4:41 ` Bryan Larsen
2005-07-18 10:22 ` Catalin Marinas
2005-07-18 18:59 ` Junio C Hamano
2005-07-18 20:57 ` Frank Sorenson
2005-07-19 0:10 ` Junio C Hamano [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=7vy883lkoz.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=bryan.larsen@gmail.com \
--cc=catalin.marinas@gmail.com \
--cc=frank@tuxrocks.com \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).