Re: [PATCH 2/3] git-p4: support exclude paths
- From
- Tommy Thorn <tommy-git@thorn.ws>
- Date
- Feb 3, 2008, 18:55 UTC
- Message-ID
- <47A60E20.7060909@thorn.ws>
- In-Reply-To
- <200802031941.17010.simon@lst.de>
Simon Hausmann wrote:
Show 19 quoted lines
> On Sunday 03 February 2008 10:21:05 Tommy Thorn wrote:
>
>> Teach git-p4 about the -/ option which adds depot paths to the exclude
>> list, used when cloning. The option is chosen such that the natural
>> Perforce syntax works, eg:
>>
>> git p4 clone //branch/path/... -//branch/path/{large,old}/...
>>
>> Trailing ... on exclude paths are optional.
>>
>> This is a generalization of a change by Dmitry Kakurin (thanks).
>>
>> Signed-off-by: Tommy Thorn <tommy-git@thorn.ws>
>>
>
> Acked-By: Simon Hausmann <simon@lst.de>
>
> I like it, Perforce'ish syntax. (Not that I like p4 though ;)
> Thank you.
I would appear that I have some mail server problems, so apologies if you get multiple copies.
Also, this is the first Python hacking I've tried, so it's likely that my changes needs improvement.
With these two patches, I can now use git-p4. However in a perfect world, git-p4 would:
- include support everything that a (ugly) Perforce client can do, including naming individual files and remapping things around (a sick feature that never should be used IMO), and
- not consume memory proportional to the imported files.
The former would require pervasive changes and likely break some assumptions currently made.
The latter is easy enough.
Regards Tommy