git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tommy Thorn <tommy-git@thorn.ws>
To: Simon Hausmann <simon@lst.de>, git@vger.kernel.org
Subject: Re: [PATCH 2/3] git-p4: support exclude paths
Date: Tue, 12 Feb 2008 07:53:38 -0800	[thread overview]
Message-ID: <47B1C102.7020400@thorn.ws> (raw)
In-Reply-To: <48092.216.228.112.21.1199496008.squirrel@numba-tu.com>

On Sunday 03 February 2008 10:21:05 I 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>

.. 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

**

       reply	other threads:[~2008-02-12 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48092.216.228.112.21.1199496008.squirrel@numba-tu.com>
2008-02-12 15:53 ` Tommy Thorn [this message]
2008-02-15 22:56   ` [PATCH 2/3] git-p4: support exclude paths Simon Hausmann
2008-02-03  9:21 [PATCH 1/3] git-p4: Fix an obvious typo Tommy Thorn
2008-02-03  9:21 ` [PATCH 2/3] git-p4: support exclude paths Tommy Thorn
2008-02-03 18:41   ` Simon Hausmann
2008-02-03 18:55     ` Tommy Thorn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47B1C102.7020400@thorn.ws \
    --to=tommy-git@thorn.ws \
    --cc=git@vger.kernel.org \
    --cc=simon@lst.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).