From: Alex Riesen <raa.lkml@gmail.com>
Date: Fri, 10 Aug 2007 08:10:59 GMT
Subject: Re: git-p4 question
Message-ID: <81b0412b0708100110w6ff90215gd5c367fb65e2ae21@mail.gmail.com>
In-Reply-To: <81b0412b0708100106m3123a504p16309b6e06cd9609@mail.gmail.com>

On 8/10/07, Alex Riesen <raa.lkml@gmail.com> wrote:
> On 8/10/07, Govind Salinas <govindsalinas@gmail.com> wrote:
> > If I can just sync from p4 and then sync my binary share and THEN tell
> > git-p4 that //depot/my/product/... maps to c:\path\src\realworkhere,
> > get it to import history etc,  then I would be set.
>
> git-p4-import.bat can import a state from the client have-list,
> but it does not import the history. It can import the history
> separately, so that you can stitch it into a merge which will be
> the state imported from the client. Complicated, but I couldn't
> bring myself to figure out the history automatically.

Err, example:

Import a state from p4 client:

  git-p4-import -y -c client-name -e

Import p4 history of a path mapping:

  git-p4-import --p4-path //perforce/path \
    --local-path very-local-path \
    --p4-range '@1234,5678' \
    --start start-commit \
    --branch branch-name

The last argument (--branch) is optional, will just store the last imported
commit there. start-commit will be assumed current HEAD, if omitted.