From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"David Tweed" <david.tweed@gmail.com>,
"Reece Dunn" <msclrhd@googlemail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Make "git reset" a builtin. (incomplete)
Date: Thu, 23 Aug 2007 12:30:47 -0400 [thread overview]
Message-ID: <9e4733910708230930k3f6d1b4i47d03753bc0d3c1@mail.gmail.com> (raw)
In-Reply-To: <20070823112413.GJ7267@thunk.org>
On 8/23/07, Theodore Tso <tytso@mit.edu> wrote:
> I don't know enough about LUA to say for sure. Having taken a quick
> look at lua.org, the implementation looks pleasantly small, and LUA
> scripts look more comprehensible than say Tcl (which is not saying
> much, I know). But part of "show me the code" is people demonstrating
> that no really, LUA is an appropriate tool for simple scripts that is
> portable enough that we don't need to have external dependencies on
> bash and perl, and that it is easier than rewriting all of our shell
> scripts in C. Maybe that is a true statement. I don't know. My
> suggestion to "Show us the code" was a way of hoping someone who cared
> enough about this issue could show us.
I just threw LUA out as an example of a tiny language in the hope of
avoiding something giant like mono. LUA is already installed on most
Linux distributions, liblua50.so on mine. It is 100KB.
LUA is used as a scripting language in some popular games. Because of
that it has good ports to Mac/Windows. There are over a dozen books on
Amazon about using LUA.
I only care about the scripting issue in that I don't want git to get
tied to a giant scripting system. LUA is small enough to package with
git.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-08-23 16:30 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 [this message]
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
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=9e4733910708230930k3f6d1b4i47d03753bc0d3c1@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=david.tweed@gmail.com \
--cc=git@vger.kernel.org \
--cc=msclrhd@googlemail.com \
--cc=tytso@mit.edu \
/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).