Jonathan Nieder <jrnie...@gmail.com> writes: > Ramkumar Ramachandra wrote: >>> Thomas Ferris Nicolaisen <tfn...@gmail.com> writes: > >>>> At least according to the documentation[1], "Git natively supports [...] >>>> ftp". >>>> >>>> This could need some clarification if pushing over ftp is not supported. > [...] >> -Git natively supports ssh, git, http, https, ftp, ftps, and rsync >> -protocols. The following syntaxes may be used with them: >> +Git natively supports ssh, git, http, https, and rsync protocols. The >> +following syntaxes may be used with them: > > Perhaps the initial list should not be exhaustive, in which case we > could say: > > Git natively supports ssh, git, http, and https protocols. The > following syntaxes may be used with them: > > ... > > Git also has (less efficient) support for fetching and pushing > over rsync protocol and fetching over ftp or ftps, using the > same "protocol://host/path/to/repo.git/" syntax.
Yeah, that, possibly with "These are deprecated; do not use them.", would be a better way forward. As we deprecated "rsync" long time ago, perhaps we should remove it at Git 2.0 or somewhere around that. By the way, that old patch by Ram in question was *not* incorrect per-se back then when dumb http was still more prevalent option between the two http transports. Fetching over dumb http and dumb ftp were both equally bad ;-) It just has become less relevant as more people start equating http with the smart http, where there is no equivalent "smart ftp". -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
