From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Josef Wolf <jw@raven.inka.de>,
git@vger.kernel.org, Petr Baudis <pasky@suse.cz>
Subject: Re: Problems using perl's Git.pm module
Date: Thu, 2 Dec 2010 18:30:03 +0100 [thread overview]
Message-ID: <AANLkTim7kTYJwnMdOD10D1o11xH7yuZXz1ZvabFL9ujE@mail.gmail.com> (raw)
In-Reply-To: <20101202161955.GB3962@burratino>
On Thu, Dec 2, 2010 at 17:19, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Ævar Arnfjörð Bjarmason wrote:
>> On Thu, Dec 2, 2010 at 12:40, Josef Wolf <jw@raven.inka.de> wrote:
>
>>> I am trying to use perl's Git.pm module, but for some reason, it keeps
>>> bailing out:
>>
>> Why are you using it? It's for internal use only.
>
> Where do you get that from? (Not sure whether it's true, just curious.)
It, like our internal C is subject to change at any time. It's not
intended for external use.
>> Couldn't you use one of the Perl Git wrappers on the CPAN?
>
> This is still a reasonable suggestion, certainly.
Yes, it really is much better to use the CPAN modules that wrap
Git. We might even want to use them ourselves someday.
next prev parent reply other threads:[~2010-12-02 17:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 11:40 Problems using perl's Git.pm module Josef Wolf
2010-12-02 13:23 ` Ævar Arnfjörð Bjarmason
2010-12-02 16:19 ` Jonathan Nieder
2010-12-02 17:30 ` Ævar Arnfjörð Bjarmason [this message]
2010-12-02 17:46 ` Junio C Hamano
2010-12-02 18:10 ` demerphq
2010-12-02 18:14 ` Jonathan Nieder
2010-12-02 18:41 ` demerphq
2010-12-02 19:05 ` [RFC/PATCH] Git.pm: discourage casual use Jonathan Nieder
2010-12-02 19:30 ` Junio C Hamano
2010-12-02 19:45 ` Jonathan Nieder
2010-12-03 8:38 ` Problems using perl's Git.pm module Josef Wolf
2010-12-03 9:02 ` demerphq
2010-12-02 18:18 ` Junio C Hamano
2010-12-02 18:32 ` demerphq
2010-12-03 8:27 ` Josef Wolf
2010-12-03 9:10 ` Jonathan Nieder
2010-12-02 17:51 ` Junio C Hamano
2010-12-03 8:14 ` Josef Wolf
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=AANLkTim7kTYJwnMdOD10D1o11xH7yuZXz1ZvabFL9ujE@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=jw@raven.inka.de \
--cc=pasky@suse.cz \
/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).