Re: Unresolved issues #2

From: sean <seanlkml@sympatico.ca>
Date: May 6, 2006, 16:53 UTC
Message-ID: <BAYC1-PASMTP0824AA77198F95FE28B79DAEAA0@CEZ.ICE>
In-Reply-To: <Pine.LNX.4.64.0605060923050.16343@g5.osdl.org>

On Sat, 6 May 2006 09:30:48 -0700 (PDT) Linus Torvalds <torvalds@osdl.org> wrote:

Show 6 quoted lines

> Basically, it boils down to the end result.
> 
> If you design things for "people", then things tend to become hard to 
> automate, and it's hard to make wrappers around it. Maybe you've even made 
> the interfaces interactive, and thus any wrappers around it are simply 
> screwed, or need to do insane things.

Okay, I mistook the scope of you comments to apply to all of git rather than as a reminder that we can't forget about the toolkit design. So I take it you're not at all against git including higher level user commands; just so long as they're built on top of lower level toolkit commands that other porcelain can use as well.

In this particular case I see "git repo-config" as the low level command that any porcelain can use to access the remotes information and the proposed "git remotes" as a simple convenience wrapper on top of this. Of course, everyone has to agree on the config file format; but that is true whether the human-friendly wrapper exists or not.

Sean