[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] strategy/code for migrating changesets out of arch

From: David Allouche
Subject: Re: [Gnu-arch-users] strategy/code for migrating changesets out of arch
Date: Sun, 7 Mar 2004 01:53:20 +0100
User-agent: Mutt/

On Mon, Feb 23, 2004 at 12:24:55PM -0800, Dustin Sallings wrote:
>       At work, we use perforce.  It's good enough when it and the network 
> works, so I've not been pushing arch to my group.  I have, however, 
> been trying to use it myself.  In doing so, I've created a utility to 
> migrate changesets applied to a particular section of a depot 
> overlapping an arch tree back into arch.  It works pretty well and I 
> seem to be getting all of our checkins into my arch mirrors.
>       Although I can branch this tree and work in it just fine, I don't 
>       have anything to reapply those changesets back into a p4 tree.  Does 
> anyone 
> have anything that might help comprehend arch changesets so I can apply 
> the changes back to p4?
>       Ideally, a python class I can ask for new files, deleted files, 
> modified files, etc... might be good...or to just iterate the changes.  
> Migrating from p4, I'm using p4lib, which gives me file-level changes 
> within a changeset by file including operation.  I translate those p4 
> operations to tla operations using the following map:

What you want is there:


Not yet perfect, not yet complete, and stalled at the moment. But still
a long way towards your goal.

The goal of that effort is to become the standard python-arch binding
module, unifying the code base of all those python-based arch tools,
using a binding layer ranging from really crappy (cscvs), to merely
adequate (tla_load_dirs). I suppose I should put in more effort if I
want to reach that goal, though...

                                                            -- ddaa

reply via email to

[Prev in Thread] Current Thread [Next in Thread]