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
