From: Shawn Pearce <spearce@spearce.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: sean <seanlkml@sympatico.ca>,
keithp@keithp.com, hpa@zytor.com, jbglaw@lug-owl.de,
git@vger.kernel.org
Subject: Re: Errors GITtifying GCC and Binutils
Date: Thu, 23 Mar 2006 15:48:25 -0500 [thread overview]
Message-ID: <20060323204825.GE30176@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603231134160.26286@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> wrote:
>
> On Thu, 23 Mar 2006, sean wrote:
> >
> > lol, that sounds like a really good plan. Perhaps as a two pronged effort
> > its worth changing the notion that git is primarily "plumbing". Adding
> > some of the nice features of cogito and other "porcelains" into the core
> > git might go a ways toward converting the few naysayers we don't kill.
>
> Actually, as far as I can tell, git already has a hell of a lot more
> porcelain than pretty much any non-IDE type traditional SCM. Certainly
> more than CVS.
>
> Yeah, I'm not counting things like Eclipse etc. I'm talking about "plain
> SCM" environments, ie just basic SVN or CVS. What are we missing in that
> department? (The only thing I can think of is a diff colorizer, which some
> prople seem to really want).
A pretty native point-and-click Windows GUI so Windows users can
use GIT without knowing how to actually use their computer. :-)
I'm not trying to bash Windows users. I'm just saying that there's
definately a large user base for SCMs such as CVS who just want
to check in the latest version of a file they have to maintain.
Many of these people are afraid of a command prompt. Asking them
to install Cygwin just to check in a file is a difficult challenge.
And even if a user is perfectly comfortable with a command prompt
and could write one-line scripts faster than anyone else, sometimes
users just prefer a GUI interface.
qgit probably comes close in this department but hasn't been packaged
up into a pretty Windows installer. :-)
But your definately right; once the blame/annotate war settles out
GIT will have pretty much everything one might need - except a good
distributed bug/issue tracking type system. :-)
--
Shawn.
next prev parent reply other threads:[~2006-03-23 20:48 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 13:33 Errors GITtifying GCC and Binutils Jan-Benedict Glaw
2006-03-22 23:39 ` Linus Torvalds
2006-03-23 0:12 ` Linus Torvalds
2006-03-23 1:28 ` Linus Torvalds
2006-03-23 20:03 ` Jan-Benedict Glaw
2006-03-23 20:42 ` Linus Torvalds
2006-03-24 0:39 ` Chris Shoemaker
2006-03-24 6:12 ` Keith Packard
2006-03-24 7:52 ` Jan-Benedict Glaw
2006-03-25 0:37 ` Chris Shoemaker
2006-03-23 6:09 ` H. Peter Anvin
2006-03-23 15:45 ` Keith Packard
2006-03-23 16:01 ` Linus Torvalds
2006-03-23 18:12 ` sean
2006-03-23 18:12 ` sean
2006-03-23 20:38 ` Linus Torvalds
2006-03-23 20:48 ` Shawn Pearce [this message]
2006-03-23 21:11 ` Ryan Anderson
2006-03-24 0:15 ` Junio C Hamano
2006-03-23 23:30 ` Junio C Hamano
2006-03-24 15:12 ` Johannes Schindelin
2006-03-24 11:11 ` Mark Wooding
2006-03-24 11:29 ` Andreas Ericsson
2006-03-23 21:31 ` David S. Miller
2006-03-23 21:48 ` Linus Torvalds
2006-03-23 22:36 ` Timo Hirvonen
2006-03-23 22:05 ` sean
2006-03-23 22:05 ` sean
2006-03-24 12:32 ` Ralf Baechle
2006-03-24 12:59 ` missing git features (was: Re: Errors GITtifying GCC and Binutils) Andreas Ericsson
2006-03-24 16:44 ` Carl Worth
2006-03-24 18:55 ` missing git features Andreas Ericsson
2006-03-23 21:02 ` Errors GITtifying GCC and Binutils Ryan Anderson
2006-03-23 21:39 ` Linus Torvalds
2006-03-23 23:51 ` Junio C Hamano
2006-03-24 0:06 ` Ryan Anderson
2006-03-24 0:34 ` Junio C Hamano
2006-03-24 12:44 ` Ralf Baechle
2006-03-24 18:25 ` Jan-Benedict Glaw
2006-03-24 19:10 ` Andreas Ericsson
2006-03-25 10:17 ` Jan-Benedict Glaw
2006-03-24 19:35 ` Santi Béjar
2006-03-25 8:25 ` Eric Wong
2006-03-26 2:52 ` [PATCH] contrib/git-svn: stabilize memory usage for big fetches Eric Wong
2006-03-25 9:10 ` Errors GITtifying GCC and Binutils James Cloos
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=20060323204825.GE30176@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=jbglaw@lug-owl.de \
--cc=keithp@keithp.com \
--cc=seanlkml@sympatico.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.