Download subdirectory from remote repository

[anatoly techtonik]

On Wed, Dec 5, 2012 at 3:54 PM, Paul Boddie <paul.boddie at biotek.uio.no>wrote:

>
> As far as the URL scheme is concerned, I imagine that something close to
> the existing "file" or "raw-file" mode is best. For example:
>
> http://selenic.com/repo/hg/**file/5cafcac2414c/doc<http://selenic.com/repo/hg/file/5cafcac2414c/doc>(currently shows the doc directory as HTML)
> http://selenic.com/repo/hg/**raw-file/5cafcac2414c/doc<http://selenic.com/repo/hg/raw-file/5cafcac2414c/doc>(currently shows the doc directory as text)
> http://selenic.com/repo/hg/**archive/5cafcac2414c.tar.gz<http://selenic.com/repo/hg/archive/5cafcac2414c.tar.gz>(currently provides all files as an archive)
> http://selenic.com/repo/hg/**archive/5cafcac2414c/doc.tar.**gz<http://selenic.com/repo/hg/archive/5cafcac2414c/doc.tar.gz>(would provide the doc directory as an archive)
>
> There's always the matter of the resource name and whether it's good
> enough, but I suppose the "Content-Disposition" header could be sent with
> something like "5cafcac2414ec-doc.tar.gz" and the archive would actually
> unpack to a directory called "5cafcac2414c-doc" so that the client could
> take the opportunity to use the appropriate name.
>

This scheme seems to work with hg-web only.

P.S. Seeing how the raw form of a directory is a textual listing, it
> reminds me of how with a bit of content preference magic and the ability to
> generate XML listings, one could support WebDAV and have a Web repository
> navigable in a suitably capable file manager, but I'm not volunteering to
> make that happen. ;-)
>

I don't know why WebDAV exists at all when there is FTP.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20121207/e848df2f/attachment-0002.html>