Re: git-p4import.py robustness changes

From: Junio C Hamano <junkio@cox.net>
Date: Jun 2, 2007, 23:52 UTC
Message-ID: <7vr6otoqw5.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <87F9A283-C51F-49FB-9A13-40E850AC0474@slamb.org>

Scott Lamb <slamb@slamb.org> writes:

Show 10 quoted lines

> On Jun 2, 2007, at 2:33 PM, Junio C Hamano wrote:
>
>> A much more preferable alternative is for you to say "Hey, don't
>> say you want to demote it.  I'll keep it maintained, I regularly
>> use p4 and have a strong incentive to keep it working".  Then we
>> do not have to do the "patch 0" ;-)
>
> Hmm. I'd like to say that, but keep in mind that I'd never even used
> git before Wednesday, and I'm not sure yet how well git-p4import.py
> will work out for me.

Oh, you do not have to worry so much. There certainly are people who are familiar enough with git on this list to help improving p4import from the git side.

The thing to me personally is that I am p4 illiterate. However, as you might be aware, a few people posted their own version of "better than p4import" scripts to the list in the past few months, so there should also be enough people with p4 expertise and motivation to help you with it.

It _might_ turn out that one of their scripts might be better than the p4import we have in-tree and we would end up replacing it with it. I won't be able to judge that myself, but if people who need to interoperate with p4 on the list can join forces it would be good.