From: Jason Riedy <ejr@EECS.Berkeley.EDU>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Stefan Pfetzing <stefan.pfetzing@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Git 1.3.2 on Solaris
Date: Tue, 16 May 2006 20:26:24 -0700 [thread overview]
Message-ID: <4973.1147836384@lotus.CS.Berkeley.EDU> (raw)
In-Reply-To: <Pine.LNX.4.64.0605161904260.16475@g5.osdl.org>
And Linus Torvalds writes:
-
- The complete libification will take some time, and in the meantime, a few
- silly C files that hard-code the shell logic is probably much preferable
- to using the shell and all the problems that involves (like the whole
- problem with quoting arguments - just _gone_ when you do it as a execve()
- in a simple C program).
But for recommending and using git on these systems _now_...
Simply translating the shell script into C with execs doesn't
help if you're execing one of the known problems, or if the
script has embedded, non-trivial Perl. git-clone is the major
blocker; a trivial translation would be a great step but won't
let people without GNU utilities clone repos.
Plus, alas, Perl modules and Python version drift can be a bit
of a problem on the same semi-pristine (or unmaintained, or
too-stable) systems, so shell isn't the only thing that needs to
go. And that'll take a good deal of effort.
Note that my code snippets weren't a suggested patch. I wouldn't
want the easy way out to impede progress on the right thing.
But some local installations may find it much easier to patch git
than to instruct users to change their utilities to match what git
expects, especially if users have old scripts that would break
if they changed their path globally. Luckily, git makes it really
easy to keep those patches locally...
Jason
next prev parent reply other threads:[~2006-05-17 3:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 23:52 Git 1.3.2 on Solaris Stefan Pfetzing
2006-05-17 1:25 ` Jason Riedy
2006-05-17 2:20 ` Linus Torvalds
2006-05-17 3:26 ` Jason Riedy [this message]
2006-05-17 3:49 ` Linus Torvalds
2006-05-17 8:05 ` Stefan Pfetzing
2006-05-17 14:33 ` Linus Torvalds
2006-05-17 15:08 ` Stefan Pfetzing
2006-05-17 16:24 ` Linus Torvalds
2006-05-17 16:35 ` Jason Riedy
2006-05-23 3:20 ` Stefan Pfetzing
2006-05-23 4:51 ` Jason Riedy
2006-05-23 12:04 ` Stefan Pfetzing
2006-05-23 14:53 ` Linus Torvalds
2006-05-23 15:20 ` Edgar Toernig
2006-05-23 15:31 ` Linus Torvalds
2006-05-23 18:43 ` Edgar Toernig
2006-05-23 18:03 ` Jason Riedy
2006-05-23 18:24 ` Linus Torvalds
2006-05-23 18:48 ` Linus Torvalds
2006-05-26 3:30 ` Stefan Pfetzing
2006-05-17 5:15 ` Ryan Anderson
2006-05-17 8:22 ` Junio C Hamano
2006-05-17 9:03 ` Junio C Hamano
2006-05-17 9:54 ` [PATCH] builtin-grep: workaround for non GNU grep Junio C Hamano
2006-05-17 14:24 ` Linus Torvalds
2006-05-17 17:41 ` Junio C Hamano
2006-05-17 15:39 ` Bertrand Jacquin
2006-05-17 17:42 ` Junio C Hamano
2006-05-17 18:12 ` Linus Torvalds
2006-05-17 18:59 ` Junio C Hamano
2006-05-17 19:42 ` Linus Torvalds
2006-05-17 8:28 ` Git 1.3.2 on Solaris Junio C Hamano
2006-05-17 9:06 ` Stefan Pfetzing
2006-05-17 9:22 ` Junio C Hamano
2006-05-17 10:41 ` Stefan Pfetzing
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=4973.1147836384@lotus.CS.Berkeley.EDU \
--to=ejr@eecs.berkeley.edu \
--cc=git@vger.kernel.org \
--cc=stefan.pfetzing@gmail.com \
--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 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).