Re: State of Perforce importing.

From: David Brown <git@davidb.org>
Date: Sep 18, 2007, 23:19 UTC
Message-ID: <20070918231921.GA17652@old.davidb.org>
In-Reply-To: <3f4fd2640709181053t70b7abcdi2c4eaf67e7b75338@mail.gmail.com>

On Tue, Sep 18, 2007 at 06:53:45PM +0100, Reece Dunn wrote:

>The main issues with using client workspaces is that they require you
>to use `p4 sync`, whereas git-p4 uses `p4 print` and that they may
>change as the repository changes, but Perforce does not track these
>changes.

Unfortunately, we have one project that heavily abuses P4 client specs. For every release, someone creates a >900 line client spec and labels the files in it. Those are the versions that need to get checked in, and without rewriting much of what P4 does, I'm going to have to let P4 do the syncing and checking out.

>I would not do that. It is a good idea to keep the original log
>messages, even if it does make for an uninformative shortlog. Look at
>some of the CVS/SVN imported logs!

I think what I want then is something to filter between 'git log' and 'git shortlog' that would find a summary line in the commit message and copy it to the top. It wouldn't change the history, but clean it up for shortlog's purpose.

David