Hello, The script attached is a 250 lines code in TCL that imports a cvs project into fossil. I am sure that it will be easy for you to adapt to svn. Feel free to do whatever you want with it.
The capabilities of the script are as follow:
1- It can import one or several cvs projects into one fossil
repository. Maintaining or
not the subdirectory names of every project
2- It makes a simple commit for several files that were committed together
3- It keeps tag and branch information
4- It works for local or remote cvs repositories
5- It takes several hours to run for a typical several-years cvs project
6- It is possible to specify the encoding of the cvs repository, so
everything gets translated into utf-8 which is what fossil accepts
7- It has been tested with several projects, some of them with more
that 10 years
history, and it works well
8- You have a unique opportunity to learn TCL and Sqlite (if you
already do not know)
Regards,
Ramon
2009/11/19 Joshua Paine <jos...@letterblock.com>:
> On Thu, 2009-11-19 at 19:33 +0000, James Gruessing wrote:
>> There's only one problem with that, and that is, how do you plan on
>> handling forks and mergers, as well as multiple branches?
>
> I don't! I haven't seen the history of the repo I need must pressingly
> to import, but with less than 150 revisions total (in SVN revision
> numbers increment across the entire repo, which includes all branches
> and may even include completely distinct projects), and given the
> intense awkwardness of merging in SVN until relatively recently, I'd be
> surprised if there are even any long-lived branches in this history.
> Since trunk, all branches, and all tags are equivalent to directory
> copies placed at arbitrary locations in a tree in SVN, it would be very
> hard to write a script that could handle branching automatically. E.g.,
> your trunk might be in /foo/trunk and your branches might be
> like /foo/branches/BRANCH_1 or /foo/BRANCH_1
> or /foo/HINDI_WORD_FOR_BRANCHES/BRANCH_1 or whatever.
>
> Anyway, I would be happy to use a script that could handle branching,
> but for my purposes just following /foo/trunk will probably be good
> enough.
>
> --
> Joshua Paine
> LetterBlock: Web applications built with joy
> http://letterblock.com/
> 301-576-1920
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
cvs_to_fossil.tcl
Description: Tcl script
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
