On Wed, Jan 30, 2008 at 07:40:02PM +0100, Vadim Lebedev wrote: > The problem is that full conversion of svn to mercurial generates > repository of 300 Mb (Orginal SVN is 700MB) > It is not practical i believe. Hmm, I'd say size shouldn't matter too much. I'm in favour of retaining all the history. These days 300 MB isn't much (fits on a CD ;-)
On Wed, Jan 30, 2008 at 06:59:49PM +0100, Darshaka Pathirana wrote: > On 25.01.2008 20:18, Vadim Lebedev wrote: > > Independently i'm struggling with the fact that mercurial does not > > support subprojects so i'd like to pickup your brains for > > suggestions on how to organize mercurial repos for the openwengo > > project > > I would like to help you but unfortunatly I am not (yet) completely > aware of the full source code. If you're able to give me some hints > and tell me what YOU mean by subprojects, that would be really > helpfull. That disclaimer applies for me, too. > - If splitting up the project, will the history of each file remain? If you split the project into sub-projects and later refactor something, then files might move from one sub-project to another. In that case history for the moved files is probably lost (or can hg retain history when moving from one repo to another? I know svn can't.). So this *might* mean that we're back to old CVS days when moving files for restructuring the repo can't be done in certain cases (umm in *all* cases for cvs :-)... So when really deciding to split, future refactoring should be kept in mind. Whats wrong with keeping a big project with subdirectories containing individual subprojects? Just my .02 Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting Fax: +43/2243/26465-23 Reichergasse 131 www: http://www.runtux.com A-3411 Weidling email: [EMAIL PROTECTED] osAlliance member email: [EMAIL PROTECTED] _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
