git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: demerphq <demerphq@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Ævar Arnfjörð" <avarab@gmail.com>,
	"Josef Wolf" <jw@raven.inka.de>,
	git@vger.kernel.org
Subject: Re: Problems using perl's Git.pm module
Date: Thu, 2 Dec 2010 19:32:21 +0100	[thread overview]
Message-ID: <AANLkTin40H-tEUScW3tuVkWkpP0gexsqM_hxBitmdZHW@mail.gmail.com> (raw)
In-Reply-To: <7v4oawrqb0.fsf@alter.siamese.dyndns.org>

On 2 December 2010 19:18, Junio C Hamano <gitster@pobox.com> wrote:
> demerphq <demerphq@gmail.com> writes:
>
>> On 2 December 2010 18:46, Junio C Hamano <gitster@pobox.com> wrote:
>>> Æ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.
>>
>> So you are saying that it is for more than internal use?
>
> No.
>
> Imagine you were adding a new function to git-svn.perl and wanted to know
> why your addition that looked somewhat similar to what Josef sent did not
> work as you expected.
>
> We should be able to answer such a question, don't you think?  People
> often seem to badmouth this list as git develper's list that is unfriendly
> to end users.  I don't think that is true, but even if that were true (or
> especially if that were true), shouldn't we be try to be friendly at least
> to a potential developer who tries to learn and use Git.pm module?

Certainly. My question purely had to do with whether it is for
internal use or not.

The reason I asked is that I don't think it is for external use, and
wanted to make sure you agree.

cheers,
Yves





-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

  reply	other threads:[~2010-12-02 18:32 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
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 [this message]
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=AANLkTin40H-tEUScW3tuVkWkpP0gexsqM_hxBitmdZHW@mail.gmail.com \
    --to=demerphq@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).