From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Josef Wolf <jw@raven.inka.de>, git@vger.kernel.org
Subject: Re: Problems using perl's Git.pm module
Date: Thu, 02 Dec 2010 09:46:23 -0800 [thread overview]
Message-ID: <7vpqtkrrtc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <AANLkTi=8=k9iNWzTnGz821k9A_CZNiEt_KkC8TXu6oS_@mail.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Thu\, 2 Dec 2010 14\:23\:32 +0100")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> 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.
That is not a valid question nor answer, I am afraid.
It probably is showing that perl/Git.pm is underdocumented. We should
make it possible if not trivial for people who want to write the next
great git-svn.perl or whatever that uses the module to interact with the
repository.
I don't understand why the Josef's scriptlet passes Directory to the
initialization code. Is it working with a bare repository?
next prev parent reply other threads:[~2010-12-02 17:46 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
2010-12-02 17:46 ` Junio C Hamano [this message]
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=7vpqtkrrtc.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jw@raven.inka.de \
/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).