Re: [PATCH v3] git-p4: add "--path-encoding" option

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 1, 2015, 17:19 UTC
Message-ID: <xmqqr3mirrau.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <523D2C52-893E-4A54-9DD1-2DDBCEA29960@gmail.com>

Lars Schneider <larsxschneider@gmail.com> writes:

Show 5 quoted lines

>> I'll move this to 9822, as 9821 is taken by another git-p4 test,
>> while queuing.
> OK. I wasn’t sure how this is handled. Just for my understanding: As
> soon as a TC number is occupied in one of the official branches
> (master/next/pu/maint) then the next number should be used, right?

That would help me great deal (as I'd be doing that if you didn't).

Show 6 quoted lines

> Two general questions:
>
> (1) I saw that the path encoding fix is already on “pu”. What is
> more convenient for you? Do you want to get a [PATCH v4] with one
> commit including the changes mentioned above or do you want me to keep
> the v3 commit and add a v4 commit on top?

The convention is to do [PATCH v$n+1] (i.e. reroll) before the topic is merged to 'next' (i.e. while in 'pu').

When further improvements are needed after the topic is merged to 'next', we switch to incremental improvements.

> (2) Is there a CI setup for Git somewhere accessible on the Internet?
> How about building and testing Git on Travis
> (https://travis-ci.org/git/git)?

Sorry but you are asking the right question to a wrong guy ;-)

There may be people who have already arranged something like that, who can speak up.