Re: git-fast-import

["Alex Riesen" <raa.lkml@gmail.com>]

On 2/6/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> Alex Riesen <raa.lkml@gmail.com> wrote:
> > On 2/6/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> > >I'm mainly worried about breaking compliation on odd architectures.
> > >gfi builds, runs and has been used for production level imports
> > >on Mac OS X, Linux and Dragonfly BSD, using both 32 bit and 64 bit
> > >architectures, but some of Git's other targets (e.g. AIX) haven't
> > >seen any testing.
> >
> > Compilation errors are the simplest to fix, just send it in.
>
> True.
>
> But it really is annoying when you download the latest-and-greatest
> release of a package only to find out it doesn't compile on your
> OS of choice, and even worse when you find out it is because of
> new code that you will never use which was added in just before
> the release went final!

Than send it now! :)

> > I have to import lots of data from perforce spaghetti, so I'm very
> > likely to try it out.
>
> I can't help you with spaghetti, but the Qt folks did make their
> Perforce importer available.  Chris Lee put it in the fast-export
> project on repo.or.cz.  Its a relatively short Python program.
> Might help you get started.

Yes, I saw their code. That's how I started thinking of using gfi
in my p4 imports.

> They created annotated tags (with no message) for every p4 changeset.
> I think its just because they didn't realize you can use (abuse?) the
> `reset` command in gfi to create lightweight tags instead.

I found it's useless to do anything with p4 changes. They lack
the most important part of history: parent. The comments get
useless too, because they refer to the most recent change,
with no practical way to extract anything in between. Not much
of a problem, nobody writes anything sensible in perforce
comments anyway.