Download subdirectory from remote repository
Paul Boddie
paul.boddie at biotek.uio.no
Fri Dec 7 12:32:59 UTC 2012
On 07/12/12 01:24, anatoly techtonik wrote:
> 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 (currently shows the doc directory as HTML)
>> 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 (currently provides all files as an archive)
>> 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.
Yes, I'm only proposing this for hgweb because I cannot influence closed
projects like Google Code, Bitbucket and SourceForge which also offer
their own Mercurial Web interfaces (that are often inferior in various
ways, anyway).
[Raw directory listings as XML for WebDAV.]
> I don't know why WebDAV exists at all when there is FTP.
One fewer service to run, one fewer port to open, uses a relatively
well-specified protocol, leverages Web server infrastructure and
capabilities, and so on.
Paul
More information about the Mercurial
mailing list