Junio C Hamano <gits...@pobox.com> writes:

> Jonathan Nieder <jrnie...@gmail.com> writes:
>
>> I'd suggest dropping ", and will soon be removed." or replacing it
>> with ". Don't use them." to avoid the question of how soon "soon" is.
>>
>> With that change and with a clearer commit message, this will probably
>> be good to go imho.
>
> Yup; thanks.

Let's do this, then.

-- >8 --
From: Ramkumar Ramachandra <artag...@gmail.com>
Subject: Git url doc: mark ftp/ftps as read-only and deprecate them

It is not even worth mentioning their removal; just discourage
people from using them.

Signed-off-by: Ramkumar Ramachandra <artag...@gmail.com>
Helped-by: Jonathan Nieder <jrnie...@gmail.com>
Signed-off-by: Junio C Hamano <gits...@pobox.com>
---
 Documentation/urls.txt | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git i/Documentation/urls.txt w/Documentation/urls.txt
index 2890194..1d15ee7 100644
--- i/Documentation/urls.txt
+++ w/Documentation/urls.txt
@@ -6,8 +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 supports ssh, git, http, and https protocols (in addition, ftp,
+and ftps can be used for fetching and rsync can be used for fetching
+and pushing, but these are inefficient and deprecated; do not use
+them).
+
+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/

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to