git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Jason Riedy <ejr@EECS.Berkeley.EDU>
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:49:54 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0605162047380.10823@g5.osdl.org> (raw)
In-Reply-To: <4973.1147836384@lotus.CS.Berkeley.EDU>



On Tue, 16 May 2006, Jason Riedy wrote:
> 
> But for recommending and using git on these systems _now_...

Yes. For that, I would literally suggest having people install the GNU 
tools (and/or a recent enough perl) somewhere early in the path.

If you use the git wrapper, for example, you can already depend on the 
fact that it will prepend the git installation directory to the path, so 
while the GNU tools might not _normally_ be on the path, if you put them 
in the same directory as your git install, you'll automatically get them 
as long as you use the "git cmd" format (rather than the "git-cmd" 
format).

		Linus

  reply	other threads:[~2006-05-17  3:50 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
2006-05-17  3:49     ` Linus Torvalds [this message]
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=Pine.LNX.4.64.0605162047380.10823@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=ejr@EECS.Berkeley.EDU \
    --cc=git@vger.kernel.org \
    --cc=stefan.pfetzing@gmail.com \
    /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).