From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Johan Herland <johan@herland.net>,
Pete Wyckoff <pw@padd.com>
Subject: Re: [PATCH 2/2] Implement git-vcs-p4
Date: Wed, 5 Aug 2009 14:32:49 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.00.0908051424370.2147@iabervon.org> (raw)
In-Reply-To: <7vocqu9mzx.fsf@alter.siamese.dyndns.org>
On Wed, 5 Aug 2009, Junio C Hamano wrote:
> Daniel Barkalow <barkalow@iabervon.org> writes:
>
> > This is probably not particularly appropriate for mainline
> > application, and is somewhat buggy, not extensively tested, and
> > incomplete, but is here as an example implementation of the API and in
> > case it is useful to other people.
>
> I do not mind carrying this in the tree, at least on 'pu', for wider
> exposure---giving easier access to others _might_ help you gain
> contributors.
>
> But we need to disable this in the Makefile by default and force
> interested parties to explicitly ask for it if we were to do that.
There are two ways it can be built: either against the API library that
Perforce distributes (without any obvious license documents) or to call
the client executable. The Makefile only tries to build against the API if
configured to have the location of it; it currently tries the client if
the API wasn't configured, but I'll make it only try even that if
configured to do so.
Alternatively, perhaps I should set up the Makefile to have a
configuration option for contrib subdirectories that need to be built? I
didn't put it in contrib/ because it (currently) needs to link against
-lgit, depend on it, and have compilation rules, and everything currently
in contrib/ is interpreted code.
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2009-08-05 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 5:02 [PATCH 2/2] Implement git-vcs-p4 Daniel Barkalow
2009-08-05 17:41 ` Junio C Hamano
2009-08-05 18:32 ` Daniel Barkalow [this message]
2009-08-05 18:45 ` Junio C Hamano
2009-08-05 18:14 ` Alex Riesen
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=alpine.LNX.2.00.0908051424370.2147@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
--cc=pw@padd.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