Thoughts on narrow checkouts
Matt Mackall
mpm at selenic.com
Wed Aug 18 00:49:30 UTC 2010
On Mon, 2010-08-16 at 14:30 +0200, Martin Geisler wrote:
> 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.
Agreed. Though if we're going to be read-only, we might as well think
ahead to narrow pulls as well.
> > 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.
Agreed. Though I'd probably do this with a config section instead.
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial-devel
mailing list