From: "André Walker" <andre@andrewalker.net>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: better way to find Git.pm officially?
Date: Thu, 29 Mar 2012 02:10:51 -0300 [thread overview]
Message-ID: <4F73EEDB.7000009@andrewalker.net> (raw)
In-Reply-To: <86r4wc9f6j.fsf@red.stonehenge.com>
On 03/29/2012 01:58 AM, Randal L. Schwartz wrote:
> Is there a simpler way? Can we get "git --perl-path" added to the
> binary or something?
Maybe after the GSoC project? :)
Although a --perl-path would probably become unnecessary for newer
versions. I guess after we publish Git.pm to CPAN, we could install it
like a regular Perl module, and just have the perl scripts use it from
default directories in @INC. Unless this will make too much trouble with
compatibility (i.e., installing Git.pm v1.9 on a machine with git v1.8
installed).
next prev parent reply other threads:[~2012-03-29 5:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 4:58 better way to find Git.pm officially? Randal L. Schwartz
2012-03-29 5:10 ` André Walker [this message]
2012-03-29 6:13 ` Jeff King
2012-03-29 6:45 ` Junio C Hamano
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=4F73EEDB.7000009@andrewalker.net \
--to=andre@andrewalker.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.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).