On Thu, Oct 11, 2007 at 03:05:01PM +0000, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
There is nothing magical with the "trunk" or "branches" directories in Subversion.
of course not, but it seems a bit odd to have branches in /branches/ and in /Pike/ and then also non branches in /Pike/
And those conventions didn't really fit the development model of Pike up until now
could you elaborate on that please? which part of the development model needs a specific layout for branches?
then all the Attics were removed.
that's something i am wondering about. why not just leave them? well, no matter, they are gone...
generally it was possible to pinpoint between which two regular commits that such an operation should be inserted. It did take a lot of detective work though, mind you.
i can believe that. i'll take a closer look at that then and see what i can make of it. hopefully i can import from svn one branch at a time and then merge them like i did with the cvs import. i'll give that a go.
See above. The files were removed using cvs remove, and then the attic was cleaned out after the split. The ,v file containing the remove operation still exists in the attic in the repository of the previous Pike version.
no, that is the confusing thing, some files that do exist in a newer version were removed from older versions.
Modifications to the repository between splits consists mostly of moves/renames since CVS provides no useable facility to do that.
detecting moves and renames was actually rather trivial. git does automatic rename detection helping me discover non-obvious moves...
greetings, martin.