Stephen Lau wrote:
I started writing some scripts to parse the Codemgr_wsdata/history file
and generate per-putback diffs from that, which could in turn be fed to
my bridge as a way of converting a workspace.
It worked for the small test project I tried it on (dep's Visual Panels
workspace), but failed to handle the larger workspaces I threw at it. I
haven't touched it in ages though...
cheers,
steve
Mike Kupfer wrote:
I was thinking it would be useful to have a script to help convert a
wx-based workspace to Mercurial. The idea was that if we have
something like
[ onnv-clone ] ----->(Steve's bridge) -----> [ hg-onnv-clone ]
| |
| | (hg clone)
| |
[ tw-proj ] [ hg-proj ]
the converter could look at the renamed, new, and active files for
tw-proj, then it could recreate those changes in hg-proj.
The first place it would be useful is for the beta-test phase for the
Mercurial-based gate. (I'm assuming that the beta-test will be run the
same way we did the beta for the Companion--a workspace is available for
people to putback to, but it gets thrown away periodically.) I think it
would make it easier to create realistic Mercurial project workspaces
that people could do practice putbacks with.
The second place it would be useful is for work that is in-progress and
under Teamware at the time we switch the gate from Teamware to
Mercurial.
What do you think? Would such a script be useful? Is the above
description a reasonable way to do it?
As Steve said, using the bridging has pitfalls as well as benefits.
Now, what should be possible is to take a wx backup (files + active list),
and apply that to a mercurial workspace in some automated fashion. I
appreciate you'll lose project history in such a scheme however, unless your
active list comments are unnaturally verbose. (I think this is what was
initially said).
Forest may complicate this somewhat (actually, I think it may complicate a
lot of stuff, but I haven't looked in enough detail to say for sure).
-- Rich
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
