Re: [PATCH 2/3] git-p4: support exclude paths
- From
- Tommy Thorn <tommy-git@thorn.ws>
- Date
- Feb 12, 2008, 15:53 UTC
- Message-ID
- <47B1C102.7020400@thorn.ws>
- In-Reply-To
- <48092.216.228.112.21.1199496008.squirrel@numba-tu.com>
On Sunday 03 February 2008 10:21:05 I wrote:
Show 11 quoted lines
> 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>.. to which Simon replied:
> Acked-By: Simon Hausmann <simon@lst.de> > > I like it, Perforce'ish syntax. (Not that I like p4 though ;)
Alas, this change needs more work - the exclude paths needs to be maintained in the commit messages as otherwise we pull in new files in the excluded path. I haven't done this yet.
However, the other patch (git-p4: no longer keep all file contents while cloning) is IMO critical. You simply cannot clone a non-trivial Perforce repository without it. Why is this being ignored? Are there no users of git-p4?
Tommy
**