From: Sean <seanlkml@sympatico.ca>
To: linux@horizon.com
Cc: hanwen@xs4all.nl, git@vger.kernel.org
Subject: Re: multi-project repos (was Re: Cleaning up git user-interface
Date: Fri, 17 Nov 2006 00:42:10 -0500 [thread overview]
Message-ID: <BAYC1-PASMTP0363A52FA4E6EE87232B20AEE80@CEZ.ICE> (raw)
In-Reply-To: <20061117051157.27896.qmail@science.horizon.com>
On 17 Nov 2006 00:11:57 -0500
linux@horizon.com wrote:
> "The only intuitive user interface is the nipple; all else is learned."
The thing is that other SCM's like hg look a lot more like a nipple than
Git. And they have the same conceptual models, more or less, to deal with
as Git.
So why is it so many people think Git has a UI problem where the same
complaint isn't levelled at Mercurial? The thing is, the focus of
Git has been different, it's been about creating great plumbing. It's
had great success at doing that, and anyone who warms up to Git is well
rewarded with a tool that gives them a lot of power and flexibility.
But Junio and others that have done most of the work have gone so far
as to say Git is basically now feature complete.. the plumbing is more
or less done.
So now it's time to make that plumbing more accessible and less
intimidating to the uninitiated. And blaming them for having the wrong
mental model is just fundamentally the wrong approach. No amount of
documentation is going to replace having tools that are the least
surprising they can be and Just Work more often than not. Other
modern SCM's have managed to do a better job of this than Git, and
there's no reason Git can't do better than it has.
As long as no damage is done to the underlying architecture and
principles of Git there really shouldn't be _any harm_ in trying
to do a better job of the porcelain layer.
next prev parent reply other threads:[~2006-11-17 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 5:11 multi-project repos (was Re: Cleaning up git user-interface linux
2006-11-17 5:42 ` Sean [this message]
2006-11-17 10:02 ` Johannes Schindelin
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=BAYC1-PASMTP0363A52FA4E6EE87232B20AEE80@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
--cc=linux@horizon.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