git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pete Wyckoff <pw@padd.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Luke Diamand <luke@diamand.org>,
	git@vger.kernel.org, Vitor Antunes <vitor.hda@gmail.com>
Subject: Re: [RFC PATCH 0/3] git-p4: move to toplevel
Date: Mon, 13 Feb 2012 18:37:06 -0500	[thread overview]
Message-ID: <20120213233706.GB29582@padd.com> (raw)
In-Reply-To: <7vwr7rgsuw.fsf@alter.siamese.dyndns.org>

gitster@pobox.com wrote on Sun, 12 Feb 2012 22:17 -0800:
> Luke Diamand <luke@diamand.org> writes:
> 
> > On 12/02/12 18:13, Pete Wyckoff wrote:
> >> The git-p4 code is in a single python script down in
> >> contrib/fast-import now.  I'd like to move it up to the top-level
> >> source directory of git to make it easier to build and
> >> distribute.  Git-p4 already takes advantage of the git
> >> infrastructure for documentation and testing, as well as the
> >> community support (Junio, many reviewers).
> >
> > About time this was done. There's still a few oddities around but far
> > fewer than there used to be. I don't know if Junio has some rules on
> > what a command needs before it graduates from contrib though.
> 
> I try not to play a dictator around here. The primary thing I hesitated so
> far about git-p4 is that it is useless if you live in the open source only
> world, iow without proprietary software.

Yes, sad.  Git-p4 at least helps people who have no choice but to
use p4, e.g., when working in a corporate environment.

It's been a big help developing git-p4 inside the git source tree
already.  Having git-p4 be an installed component would make it
easier on users.  "make install" puts the script where it goes.
Or better, they get it through their OS distribution.

		-- Pete

  reply	other threads:[~2012-02-13 23:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-12 18:13 [RFC PATCH 0/3] git-p4: move to toplevel Pete Wyckoff
2012-02-12 18:13 ` [RFC PATCH 1/3] " Pete Wyckoff
2012-02-12 18:13 ` [RFC PATCH 2/3] git p4: update name in script Pete Wyckoff
2012-02-12 18:13 ` [RFC PATCH 3/3] git p4: use "git p4" directly in tests Pete Wyckoff
2012-02-12 18:54 ` [RFC PATCH 0/3] git-p4: move to toplevel Luke Diamand
2012-02-13  6:17   ` Junio C Hamano
2012-02-13 23:37     ` Pete Wyckoff [this message]
2012-02-13 20:00 ` Junio C Hamano
2012-02-13 20:37   ` Clemens Buchacher
2012-02-13 21:20     ` Junio C Hamano
2012-02-13 23:32       ` Pete Wyckoff
2012-02-14  9:20       ` Clemens Buchacher
2012-02-14 18:40         ` Junio C Hamano
2012-02-14 19:05           ` Jeff King
2012-02-14 19:25             ` Junio C Hamano
2012-02-14 19:49             ` Clemens Buchacher

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=20120213233706.GB29582@padd.com \
    --to=pw@padd.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=luke@diamand.org \
    --cc=vitor.hda@gmail.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;
as well as URLs for NNTP newsgroup(s).