How to organize a 'central repository'

Michael Smith michael.smith at
Mon Mar 31 16:30:35 CDT 2008

David I. wrote:
> Brian,
> Could you post some info on how you got Tailor configured to convert 
> your repository?

I sent Brian the following tailor config a couple of weeks ago. I don't 
know if it worked for him though.

My working config:

verbose = False
encoding = UTF-8
encoding-errors-policy = ignore

target = hg:target
start-revision = BRANCHNAME-2_0 INITIAL
root-directory = /path/to/clones/cvsmodulename.BRANCHNAME-2_0
state-file = tailor.state
source = cvs:source
subdir = .
patch-name-format =

repository = /path/to/repos/melbourne/cvsmodulename.BRANCHNAME-2_0

module = directory/modulename
repository = /path/to/cvsroot

...though looking at it now I am not convinced that

repository = /path/to/repos/melbourne/cvsmodulename.BRANCHNAME-2_0

is working correctly. I do a clone from 
/path/to/clones/cvsmodulename.BRANCHNAME-2_0 after importing from cvs.

Identifiers and paths have been changed but the config is otherwise correct.

Changesets in the target repo always start at the branching point. 
Everything before that is a snapshot when it gets to HG.

Michael Smith               | 61 386 304 560
Team Leader, Case and Tools | 61 416 062 898
Thales Australia TCC        |    S  37.82329
Melbourne, Victoria         |    E 144.95426
Confidentiality Notice: This e-mail may contain confidential and/or 
privileged information and is intended solely for the addressee(s) 
named. If you have received this information in error, or are advised 
that you have been posted this e-mail by accident, please notify the 
sender by return e-mail, do not redistribute it, delete the e-mail and 
keep no copies.

More information about the Mercurial mailing list