On Tue, Feb 10, 2015 at 2:00 AM, Andy Bradford < amb-sendok-1426122016.lhpdialnhmgdimmho...@bradfords.org> wrote:
> Is he not simply asking that, given: > > fossil clone newproject.fossil http://user@remote:1234/newproject > > Where /newproject does not yet exist, and then the remote Fossil > instance takes care of creating whatever is necessary on the remote side > to make /newproject a clone of the project? > Yes: that the target for the clone be able to be a remote URL (he's asking only about SSH, but in the abstract, an arbitrary protocol). > I suppose such a setup might be useful if your only access to a remote > host is via Fossil... but, why? > Can't say - i don't generally ask people why they want to implement a given solution because it's their own business ;). i think his request is fundamentally reasonable for ssh, but can't currently envision what it would take for HTTP remote targets. Having never used the ssh support, though, i can't say whether it's even remotely (no pun intended) feasible to add such a beast to the current code basis. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-dev mailing list fossil-dev@lists.fossil-scm.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/fossil-dev
