From: Scott Lamb <slamb@slamb.org>
To: Sean <seanlkml@sympatico.ca>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/4] Move git-p4import into contrib directory.
Date: Sun, 15 Jul 2007 14:53:53 -0700 [thread overview]
Message-ID: <469A9771.1000805@slamb.org> (raw)
In-Reply-To: <20070715154804.2877361d.seanlkml@sympatico.ca>
Sean wrote:
> Hi Junio,
>
> Having caught up on some list emails, it appears that Git now has a
> much better option for importing from Perforce in the git-p4 front
> end to fast-import.
>
> Is there anyone out there actually even using git-p4import? It was
> written for a very specific case, by a git wannabe hacker who had
> never used Perforce before, and not intended for inclusion in Git
> proper...
>
> My guess is that it could be removed outright without pain to anyone,
> but as a first step, it could be moved into contrib for 1.5.3.
I vote for removing it immediately. It has serious bugs - e.g.,
incremental mode is totally broken. I sent in a patch a month ago to fix
this particular bug, which remains unapplied. Now that git-p4 has made
it into git.git, I don't think anyone - myself included - is interested
in creating or merging git-p4import.py fixes. Keeping git-p4import.py in
this broken state just wastes the time of anyone unlucky enough to see
it first.
Best regards,
Scott
--
Scott Lamb <http://www.slamb.org/>
next prev parent reply other threads:[~2007-07-15 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 19:48 [PATCH 0/4] Move git-p4import into contrib directory Sean
2007-07-15 19:49 ` [PATCH 1/4] Remove "WITH_P4IMPORT" knob from the Makefile Sean
2007-07-15 19:51 ` [PATCH 2/4] Remove p4 rpm from git.spec.in Sean
2007-07-15 19:52 ` [PATCH 3/4] Demote git-p4import to contrib status Sean
2007-07-15 19:53 ` [PATCH 4/4] Update 1.5.3 release notes: git-p4import has been deprecated Sean
2007-07-15 21:53 ` Scott Lamb [this message]
2007-07-15 22:37 ` [PATCH 0/4] Move git-p4import into contrib directory Junio C Hamano
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=469A9771.1000805@slamb.org \
--to=slamb@slamb.org \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
/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.