I see the ssh implementation as a possible stepping stone to something along the lines of gitolite for fossil. The gitolite pages have some good background on using ssh for this along with a troubleshooting document that I found very helpful when setting it up (a non-trivial exercise at the time).
For reference gitolite ssh info can be found here: http://gitolite.com/gitolite/ssh.html On Wed, Jul 17, 2013 at 11:51 PM, Andy Bradford <amb-fos...@bradfords.org>wrote: > Thus said Martin Gagnon on Wed, 17 Jul 2013 08:04:10 -0400: > > > I propose to add a kind of -l|--login option to the clone command, so > > when the username@ is present but don't match the repo username, we > > could specify repo username with -l. > > While I do like this idea, at first glance it seems that it would > require a lot of code churn to make it work. The password prompting code > is all based upon who the urlUser is (username after the ssh://) and > adding an option to prompt for the password of a different user other > than the one in the URL would be a significant change I think. > > It would be simpler to add a --ssh-login instead: > > fossil clone --ssh-login <host-username> > ssh://<repo-username>@<host>//repo.fsl > > Thoughts? > > Andy > -- > TAI64 timestamp: 4000000051e7908a > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- Matt -=- 90% of the nations wealth is held by 2% of the people. Bummer to be in the majority...
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
