From: Jonathan Nieder <jrnieder@gmail.com>
To: demerphq <demerphq@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð" <avarab@gmail.com>,
"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 12:14:25 -0600 [thread overview]
Message-ID: <20101202181425.GG3962@burratino> (raw)
In-Reply-To: <AANLkTikQdw3aafsfP+SCQ-z9_TZrPJx694QOSeNTrvp6@mail.gmail.com>
demerphq wrote:
> On 2 December 2010 18:46, Junio C Hamano <gitster@pobox.com> wrote:
> > Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>>> Why are you using it? It's for internal use only.
>>
>> That is not a valid question nor answer, I am afraid.
>
> So you are saying that it is for more than internal use?
I assume so. I had guessed the same thing (that it is meant to be
generally useful), based on the following:
- it is installed to be usable with a simple "use Git"
automatically
- "perldoc Git" tells me that this module gives Perl scripts an easy
way to interface the Git version control system, not that it is an
implementation artifact
- tools like "git svn" were not historically part of core git, and
usage by them was not exactly internal use.
Hope that helps.
Jonathan
next prev parent reply other threads:[~2010-12-02 18:14 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
2010-12-02 18:10 ` demerphq
2010-12-02 18:14 ` Jonathan Nieder [this message]
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=20101202181425.GG3962@burratino \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=demerphq@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).