Repository collection practices
Thomas Arendsen Hein
thomas at intevation.de
Fri Jun 30 04:41:26 CDT 2006
* Mark White <mark at celos.net> [20060626 18:33]:
> Out of interest: what kind of working practices do people
> have for organising their collections of Hg repositories
> (which, under eg Subversion, might live in a single tree?)
For project "foo" I use something like:
foo/ - project directory
foo/Notes/ - collection of text files on various topics
foo/cvs/ - checkouts or rsynced cvs repo for conversion
foo/hg/ - no files here, just one subdir per working branch
foo/hg/clean/ - one subdir per repo cloned from other people,
often done with 'hg clone -U' and in a subdir per
person, e.g. foo/hg/clean/hopper/webmerc/
foo/hg/old/ - old working branches which I want to get out of my
way, but may contain history I want to keep
foo/patches/ - collection patches (possible subdirs like
'applied', 'obsolete' for old patches)
foo/download/ - release tarballs, dependencies and such
Thomas
--
Email: thomas at intevation.de
http://intevation.de/~thomas/
More information about the Mercurial
mailing list