From: Luke Diamand <luke@diamand.org>
To: Pete Wyckoff <pw@padd.com>
Cc: git@vger.kernel.org, Vitor Antunes <vitor.hda@gmail.com>
Subject: Re: [RFC PATCH 0/3] git-p4: move to toplevel
Date: Sun, 12 Feb 2012 18:54:19 +0000 [thread overview]
Message-ID: <4F380ADB.4090304@diamand.org> (raw)
In-Reply-To: <1329070423-23761-1-git-send-email-pw@padd.com>
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.
<snip>
> a core git package, or as a separate add-on. Getting support
> for python and git-p4 in msysgit is something I'd like to see
> happen too.
Not sure about msysgit, but last time I tried on Windows it didn't work
at all well.
>
> While I considered taking this opportunity to split up git-p4
> into more modular components across multiple files, it seems best
> now just to do the script move intact. That effort could come
> later. If anyone has a strong preference to do this now, we could.
Regards!
Luke
next prev parent reply other threads:[~2012-02-12 18:54 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 ` Luke Diamand [this message]
2012-02-13 6:17 ` [RFC PATCH 0/3] git-p4: move to toplevel Junio C Hamano
2012-02-13 23:37 ` Pete Wyckoff
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=4F380ADB.4090304@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=pw@padd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.