From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Fredrik Gustafsson <iveqy@iveqy.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org, Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [PATCH/RFC 0/7] Support for Ruby
Date: Sun, 22 Sep 2013 10:12:50 +0200 [thread overview]
Message-ID: <20130922081250.GD13262@paksenarrion.iveqy.com> (raw)
In-Reply-To: <CAMP44s0Lww+se6iA2NWSwkeuLdR9mc0ppnVBSjWu4d73YeP6oA@mail.gmail.com>
On Sun, Sep 22, 2013 at 02:43:39AM -0500, Felipe Contreras wrote:
> > It would actually be usefull to know stats on where git is runned. In my
> > world of embedded computing, ruby support definitely isn't a standard,
> > nor is glibc.
>
> I come from the embedded world as well, and I've never seen Git used there.
>
> I'd say Windows support is much more important than embedded, and we
> are not supporting that properly.
Me neither, it doesn't mean that it isn't used though... I agree with
the lack of windows support from git.git. However since Microsoft
working with libgit2 on a Visual Studio plugin this it might be that the
need for windows support decreases.
>
> >> > Also, the only Python script that is shipped with Git is git-p4, which
> >> > is essentially optional, since most git users probably do not use
> >> > Perforce. Otherwise, all the scripts in git are shell or Perl.
> >>
> >> Neither perl, nor shell, nor python scripts solve the forking problem. My
> >> proposal does.
> >
> > It does,
>
> No, it does not. All the **current** perl/shell/python scripts use
> 'git foo' commands to achieve everything.
As I said, "It does" meaning "Your solution solves the forking problem".
>
> > and so does Lua,
>
> There is no lua in Git.
There's no ruby in git either as far as I know... (and no, I don't think
contrib/ counts).
>
> > which can be bundled with git and used in the
> > configuration files as well and is pure ansi C. However bundling
> > something has it bad sides too. At least this will solve the dependency
> > problem. So let the language war begin =).
>
> Talk is cheap, show me the code.
See this thread by Jeff King:
http://thread.gmane.org/gmane.comp.version-control.git/206335/focus=206337
And see my humble test of what the speedup would be for git-submodule
even with a faulty lua integration (still forking... but huge
performance boost anyway):
http://thread.gmane.org/gmane.comp.version-control.git/228031/focus=228051
As you can see a lua integration would increase the git binary with
300kb.
--
Med vänliga hälsningar
Fredrik Gustafsson
tel: 0733-608274
e-post: iveqy@iveqy.com
next prev parent reply other threads:[~2013-09-22 8:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 18:48 [PATCH/RFC 0/7] Support for Ruby Felipe Contreras
2013-09-21 18:48 ` [PATCH/RFC 1/7] Add support for ruby commands Felipe Contreras
2013-09-21 18:48 ` [PATCH/RFC 2/7] ruby: add setup script Felipe Contreras
2013-09-21 18:48 ` [PATCH/RFC 3/7] ruby: add simple wrappers Felipe Contreras
2013-09-21 18:48 ` [PATCH/RFC 4/7] ruby: rewrite 'request-pull' Felipe Contreras
2013-09-21 18:48 ` [PATCH/RFC 5/7] ruby: rewrite perl script Felipe Contreras
2013-09-21 18:48 ` [PATCH/RFC 6/7] ruby: remove one fork Felipe Contreras
2013-09-21 18:48 ` [PATCH/RFC 7/7] ruby: rewrite 'reset' Felipe Contreras
2013-09-21 21:29 ` [PATCH/RFC 0/7] Support for Ruby brian m. carlson
2013-09-21 22:52 ` Felipe Contreras
2013-09-21 23:56 ` brian m. carlson
2013-09-22 5:36 ` Felipe Contreras
2013-09-22 7:31 ` Fredrik Gustafsson
2013-09-22 7:43 ` Felipe Contreras
2013-09-22 8:12 ` Fredrik Gustafsson [this message]
2013-09-22 8:29 ` Felipe Contreras
2013-09-23 18:20 ` Patrick Donnelly
2013-09-23 18:53 ` Felipe Contreras
2013-09-23 19:20 ` Patrick Donnelly
2013-09-23 19:47 ` Felipe Contreras
2013-09-23 0:00 ` Junio C Hamano
2013-09-23 1:41 ` brian m. carlson
2013-09-28 22:57 ` Felipe Contreras
2013-09-23 18:17 ` Felipe Contreras
2013-09-28 22:56 ` Felipe Contreras
2013-09-28 23:06 ` Felipe Contreras
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=20130922081250.GD13262@paksenarrion.iveqy.com \
--to=iveqy@iveqy.com \
--cc=artagnon@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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).