Thoughts on narrow checkouts
Martin Geisler
mg at aragost.com
Mon Aug 16 07:30:51 CDT 2010
Patrick Mézard <pmezard at gmail.com> writes:
Hi Patrick,
> I am trying to measure the feasability and amount of work to support
> read-only narrow checkouts as Mercurial subrepositories.
I think this sounds like an interesting and useful feature.
> 3- Add a new subrepo type like [hgreadonly] where the .hgsubstate
> would store the revisions as nodeid at subpath. A narrow checkout
> command may be useful too, so the "checkout then register in
> .hgsub" workflow would still be usable (instead of editing
> .hgsubstate directly).
I think it would be better to let the user specify the narrow path in
the .hgsub file and reserve the .hgsubstate file for Mercurial. I'm
imagining a format like this:
path = [type, param1: value1, param2: "value2 with spaces", ...] url
in the .hgsub file. I guess we can adapt ui.configlist to handle this,
if we decide to to with this format.
--
Martin Geisler
aragost Trifork
Professional Mercurial support
http://aragost.com/mercurial/
More information about the Mercurial-devel
mailing list