Toby Johnson wrote:
>Nathan Kidd wrote:
>
>
>
>>All that info was from a directory's perspective. When doing history
>>on a directory you still get info about the files in it. When doing a
>>
>>
>
>
>
>>single file's history I get the same results as you.
>>
>>BTW, I believe your file-based approach is better. Getting the
>>current directory layout from an SS dir, and then populating with the
>>history of current files is much easier than trying to retrace through
>>
>>
Hey guys! I'm actually the original author (plagiarist? I borrowed
heavily from cvs2svn.py) of vss2svn.py. We took the directory approach
because sadly (at through the automation interface) history on actual
files is incomplete. Believe me, parsing the text of ss.exe was not the
route of choice! I was originally trying to do it through the automation
interface as this is much easier but alas it cannot be done. Here's a
quote from the script:
> # NOTE: originally this script was written to utilize the VSS Automation
> # interface so that all this disgusting parsing of command-line output
> # would not have to be done. Unfortunately, the VSS Automation API
> # is crippled in some dire and more unfortunately, unfixable ways. You
> # can get around some of the issues. Anyhow so the command-line is used
> # to get histories on the files. For a nice in-depth read of what is wrong
> # with VSS (including but not limited to why we must use the command-line
> # tool) read http://www.michaelbolton.net/testing/VSSDefects.html
>>the directory's history.
>>
>>
>>
>OK, I see what you're saying. I believe, though, that the python script
>you refer to tried to build a "dump" file for Subversion to import,
>rather than doing live commits to Subversion in the order they
>originally occured. So that's probably why the other script took the
>directory-based approach.
>
>
yep, exactly. I took that approach basically because that was the
approach cvs2svn.py took and I kinda liked it.
>So, it looks like I still need to account for "branched" and "rolled
>back", no big deal. But Steve had encountered the following output while
>
>running my script, which is completely different than anything I
>encountered:
>
>**********************
>Label: "031013-077p-TY2"
>User: Watsone Date: 13/10/03 Time: 2:03p
>Labeled
>
>***************** Version 1 *****************
>User: Admin Date: 7/10/03 Time: 5:16p
>Created
>
>The separate section about the label is new to me, so I need to see how
>it fits in with everything else.
>
>
It's been a while since I worked on vss2svn.py (and it is by no means
finished in the sense of being fully functional though it does work for
simple cases) I think I remember that VSS doesn't actually associate a
Label with a specific revision, at least not in the sense that it is
attached to it. Cool huh?!
The bottom line with vss2svn.py is that I don't have time to work on it
right now even though I'd love to see it fully working. I would
certainly be willing to spend a little time looking at patches if you
can fix/improve anything in it.
--
Jens B. Jorgensen
jens.jorgensen@tallan.com
"With a focused commitment to our clients and our people, we deliver value through customized technology solutions"
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 20 23:45:55 2004