From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Make "git reset" a builtin. (incomplete)
Date: Thu, 23 Aug 2007 10:55:03 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708231051210.20400@racer.site> (raw)
In-Reply-To: <alpine.LFD.0.999.0708221313350.16727@xanadu.home>
Hi,
On Wed, 22 Aug 2007, Nicolas Pitre wrote:
> On Wed, 22 Aug 2007, Johannes Schindelin wrote:
>
> > What is wrong with going from shell to C? C _is_ portable. Instead
> > of relying on _yet_ another scripting language, introducing _yet_
> > another language that people have to learn to hack git, introducing
> > _yet_ another place for bugs to hide, why not just admit that shell is
> > nice for _prototyping_?
>
> This is a narrow view of the programming world that I don't share.
Well, you have to admit that some things are really, really hard to do in
shell. Just from the top of my head: locking, data structures,
portability, scalability, process control. There are a lot more, I guess,
but for the _core_ of Git I really prefer C.
> C is portable indeed, which is one of its upsides. But it has many
> downsides too for many _users_, that as a Git _developer_ you apparently
> conveniently ignore.
I do not want to shove C down the throat of every Git user. You can use
_whatever_ scripting language you like.
Nevertheless, this is _different_ from the choice for _core_ Git.
Eventually I'd like to be able to run Git on embedded systems, or my
digital watch.
> > Why do we have to to have the same discussion over and over and over
> > again?
>
> Because, as shown by the recurring nature of this discussion, using C for
> everything is evidently not the optimal solution.
I think the reason is different (as shown by the content of the
discussion).
Ciao,
Dscho
next prev parent reply other threads:[~2007-08-23 9:55 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 12:48 [PATCH] Make "git reset" a builtin. (incomplete) Carlos Rica
2007-08-22 13:00 ` David Kastrup
2007-08-22 13:37 ` Andreas Ericsson
2007-08-22 14:29 ` David Kastrup
2007-08-22 14:49 ` Mike Hommey
2007-08-22 15:02 ` Chris Shoemaker
2007-08-22 15:41 ` David Kastrup
2007-08-22 16:07 ` Nicolas Pitre
2007-08-22 16:51 ` Johannes Schindelin
2007-08-22 17:17 ` David Kastrup
2007-08-22 19:05 ` Linus Torvalds
2007-08-22 19:36 ` David Kastrup
2007-08-22 19:58 ` Linus Torvalds
2007-08-22 22:25 ` David Kastrup
2007-08-22 23:10 ` Linus Torvalds
2007-08-22 23:39 ` David Kastrup
2007-08-23 1:30 ` Linus Torvalds
2007-08-23 0:24 ` Wincent Colaiuta
2007-08-23 1:15 ` Nicolas Pitre
2007-08-23 1:40 ` Jon Smirl
2007-08-23 3:23 ` Linus Torvalds
2007-08-23 4:21 ` Junio C Hamano
2007-08-23 9:15 ` Johannes Schindelin
2007-08-22 21:34 ` Reece Dunn
2007-08-23 9:10 ` Johannes Schindelin
2007-08-23 10:20 ` Theodore Tso
2007-08-23 10:31 ` Johannes Schindelin
2007-08-23 10:55 ` David Tweed
2007-08-23 11:24 ` Theodore Tso
2007-08-23 11:35 ` Johannes Schindelin
2007-08-23 16:30 ` Jon Smirl
2007-08-23 11:25 ` Reece Dunn
2007-08-23 20:26 ` Alex Riesen
2007-08-23 21:14 ` David Kastrup
2007-08-23 21:33 ` Alex Riesen
2007-08-23 22:05 ` David Kastrup
2007-08-22 17:21 ` Nicolas Pitre
2007-08-23 9:55 ` Johannes Schindelin [this message]
2007-08-23 15:19 ` Nicolas Pitre
2007-08-22 21:19 ` Reece Dunn
2007-08-23 9:05 ` Johannes Schindelin
2007-08-23 18:40 ` Robin Rosenberg
2007-08-23 2:05 ` Nguyen Thai Ngoc Duy
2007-08-22 13:42 ` Matthieu Moy
2007-08-22 22:28 ` David Kastrup
2007-08-22 14:27 ` Andy Parkins
2007-08-22 14:57 ` Johannes Sixt
2007-08-22 16:20 ` Alex Riesen
2007-08-23 11:14 ` 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=Pine.LNX.4.64.0708231051210.20400@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=nico@cam.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).