{"thread":{"id":"12057","subject":"Re: [PATCH 2/3] git-p4: support exclude paths","startedAt":"2008-02-12T15:53:38Z","lastAt":"2008-02-15T22:56:31Z","messageCount":2,"participants":["Tommy Thorn","Simon Hausmann"],"isPatch":true,"patchVersion":1,"patchTotal":3},"messages":[{"id":"68526","messageId":"47B1C102.7020400@thorn.ws","threadId":"12057","inReplyTo":"48092.216.228.112.21.1199496008.squirrel@numba-tu.com","subject":"Re: [PATCH 2/3] git-p4: support exclude paths","fromName":"Tommy Thorn","fromEmail":"tommy-git@thorn.ws","sentAt":"2008-02-12T15:53:38Z","receivedAt":"2008-02-12T15:53:38Z","isPatch":true,"sender":{"key":"tommy-git@thorn.ws","avatar":null},"body":"On Sunday 03 February 2008 10:21:05 I wrote:\n> Teach git-p4 about the -/ option which adds depot paths to the exclude\n> list, used when cloning. The option is chosen such that the natural\n> Perforce syntax works, eg:\n>\n>   git p4 clone //branch/path/... -//branch/path/{large,old}/...\n>\n> Trailing ... on exclude paths are optional.\n>\n> This is a generalization of a change by Dmitry Kakurin (thanks).\n>\n> Signed-off-by: Tommy Thorn <tommy-git@thorn.ws>\n\n.. to which Simon replied:\n> Acked-By: Simon Hausmann <simon@lst.de>\n>\n> I like it, Perforce'ish syntax. (Not that I like p4 though ;)\n\nAlas, this change needs more work - the exclude paths needs to \nbe maintained in the commit messages as otherwise we pull in new\nfiles in the excluded path. I haven't done this yet.\n\nHowever, the other patch (git-p4: no longer keep all file contents while cloning)\nis IMO critical. You simply cannot clone a non-trivial Perforce repository \nwithout it. Why is this being ignored? Are there no users of git-p4?\n\n\nTommy\n\n**\n"},{"id":"68850","messageId":"200802152356.34841.simon@lst.de","threadId":"12057","inReplyTo":"47B1C102.7020400@thorn.ws","subject":"Re: [PATCH 2/3] git-p4: support exclude paths","fromName":"Simon Hausmann","fromEmail":"simon@lst.de","sentAt":"2008-02-15T22:56:31Z","receivedAt":"2008-02-15T22:56:31Z","isPatch":true,"sender":{"key":"hausmann@kde.org","avatar":"https://gravatar.com/avatar/bc9aad4fb31dce17eb66e690e7b51fe980c62da3c225c785da35dd806b8da778?d=mp&s=160"},"body":"On Tuesday 12 February 2008 16:53:38 Tommy Thorn wrote:\n> On Sunday 03 February 2008 10:21:05 I wrote:\n> > Teach git-p4 about the -/ option which adds depot paths to the exclude\n> > list, used when cloning. The option is chosen such that the natural\n> > Perforce syntax works, eg:\n> >\n> >   git p4 clone //branch/path/... -//branch/path/{large,old}/...\n> >\n> > Trailing ... on exclude paths are optional.\n> >\n> > This is a generalization of a change by Dmitry Kakurin (thanks).\n> >\n> > Signed-off-by: Tommy Thorn <tommy-git@thorn.ws>\n>\n> .. to which Simon replied:\n> > Acked-By: Simon Hausmann <simon@lst.de>\n> >\n> > I like it, Perforce'ish syntax. (Not that I like p4 though ;)\n>\n> Alas, this change needs more work - the exclude paths needs to\n> be maintained in the commit messages as otherwise we pull in new\n> files in the excluded path. I haven't done this yet.\n>\n> However, the other patch (git-p4: no longer keep all file contents while\n> cloning) is IMO critical. You simply cannot clone a non-trivial Perforce\n> repository without it. Why is this being ignored? Are there no users of\n> git-p4?\n\nSorry for the delay, my real life has kept be busy :)\n\nI now looked at the patch and I'm all in favour of applying it. However it \ndoesn't seem to apply against the current git-p4. Can you re-send the patch \nto me?\n\nThanks,\nSimon\n\nP.S.: I have applied the other patch (exclude path support)\n"}]}