Junio C Hamano wrote:
> 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.
I see. Will we remove ftp[s] support too? I hope this is in order.
-- 8< --
From: Ramkumar Ramachandra <artag...@gmail.com>
Date: Sun, 7 Oct 2012 20:57:15 +0530
Subject: [PATCH] Documentation/urls: mark rsync and ftp[s] as deprecated
Fetching and pushing over rsync, and fetching over ftp or ftps are
deprecated, and will soon be removed. Add a note saying this.
Helped-by: Jonathan Nieder <jrnie...@gmail.com>
Signed-off-by: Ramkumar Ramachandra <artag...@gmail.com>
---
Documentation/urls.txt | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/Documentation/urls.txt b/Documentation/urls.txt
index 2890194..653b61c 100644
--- a/Documentation/urls.txt
+++ b/Documentation/urls.txt
@@ -6,14 +6,12 @@ address of the remote server, and the path to the repository.
Depending on the transport protocol, some of this information may be
absent.
-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, and https protocols. The
+following syntaxes may be used with them:
- ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git/
- git://host.xz{startsb}:port{endsb}/path/to/repo.git/
- http{startsb}s{endsb}://host.xz{startsb}:port{endsb}/path/to/repo.git/
-- ftp{startsb}s{endsb}://host.xz{startsb}:port{endsb}/path/to/repo.git/
-- rsync://host.xz/path/to/repo.git/
An alternative scp-like syntax may also be used with the ssh protocol:
@@ -31,6 +29,11 @@ syntaxes may be used:
- /path/to/repo.git/
- file:///path/to/repo.git/
+ 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. However, these are
+ deprecated, and will soon be removed.
+
ifndef::git-clone[]
These two syntaxes are mostly equivalent, except when cloning, when
the former implies --local option. See linkgit:git-clone[1] for
--
1.7.12.1.428.g652398a.dirty
--
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
