Thoughts on narrow checkouts

Didly Bom didlybom at gmail.com
Wed Aug 18 02:42:36 CDT 2010


On Wed, Aug 18, 2010 at 2:49 AM, Matt Mackall <mpm at selenic.com> wrote:

> 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.


I also think that this could be a very useful feature!

Is there a technical reason (other than the additional development effort)
to make these narrow checkouts read only? Or could this be a first step
towards full narrow checkout support?

I think that being able to pick and choose which files you want to include
from a subrepo (and in which locations) yet still be able to change those
files and push the changes to the source repository could be very useful and
would give a lot of additional flexibility when using mercurial on  projects
that have a lot of related sub-components.

Angel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100818/43f4ce7f/attachment.htm>


More information about the Mercurial-devel mailing list