From: Tomas Carnecky <tom@dbservice.com>
To: Chris Hoogendyk <hoogendyk@bio.umass.edu>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"git mailing list" <git@vger.kernel.org>
Subject: Re: building git on Solaris
Date: Fri, 10 Sep 2010 22:00:03 +0200 [thread overview]
Message-ID: <4C8A8E43.1030708@dbservice.com> (raw)
In-Reply-To: <4C87A1DF.1020706@bio.umass.edu>
On 9/8/10 4:46 PM, Chris Hoogendyk wrote:
> Anyway, now I'm in the normal build debugging mode. Got all the way
> through to building the Documentation, at which stage I now need to get
> asciidoc and python. I don't really like bloating my minimal server
> systems with python, but it seems I'm finally stuck, since I have
> faculty who really want to use git.
Git doesn't *need* python nor asciidoc, it works just fine without.
Except, of course, that tools which require python don't work (but there
aren't many of those, most is C, shell and perl).
tom
prev parent reply other threads:[~2010-09-10 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 21:02 building git on Solaris Chris Hoogendyk
2010-09-07 21:42 ` Ævar Arnfjörð Bjarmason
2010-09-08 14:46 ` Chris Hoogendyk
2010-09-08 14:55 ` Ben Walton
2010-09-08 15:16 ` Brandon Casey
2010-09-10 20:00 ` Tomas Carnecky [this message]
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=4C8A8E43.1030708@dbservice.com \
--to=tom@dbservice.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=hoogendyk@bio.umass.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).