From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Thomas Ferris Nicolaisen <tfnico@gmail.com>,
Philippe Vaucher <philippe.vaucher@gmail.com>,
Konstantin Khomoutov <flatworm@users.sourceforge.net>,
git@vger.kernel.org, git-users@googlegroups.com,
August Karlstrom <fusionfile@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: Fw: [git-users] How do I git-push to an FTP server?
Date: Mon, 8 Oct 2012 12:53:18 +0530 [thread overview]
Message-ID: <CALkWK0nSxBsiE5_BZ67dPrwDRQSipL0LBR9Pf252iqL21HwZBA@mail.gmail.com> (raw)
In-Reply-To: <7vvcemovrh.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>
>> Ramkumar Ramachandra wrote:
>>>> Thomas Ferris Nicolaisen <tfnico@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 <artagnon@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 <jrnieder@gmail.com>
Signed-off-by: Ramkumar Ramachandra <artagnon@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
next prev parent reply other threads:[~2012-10-08 7:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 13:38 Fw: How do I git-push to an FTP server? Konstantin Khomoutov
2012-10-05 13:46 ` Fw: [git-users] " Philippe Vaucher
[not found] ` <CAGK7Mr4L0Us3ykLUoWBdyR2zJUNa_HNguwb-=dEq_h_yXThPPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-05 15:21 ` Fw: " Thomas Ferris Nicolaisen
[not found] ` <CAEcj5uW4aw19MgNi8vJk5TWoL6SEad=s2jthS-h1jLTtuPq7AQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-05 21:48 ` Junio C Hamano
2012-10-07 15:28 ` Fw: [git-users] " Ramkumar Ramachandra
2012-10-07 17:27 ` Jonathan Nieder
[not found] ` <20121007172754.GA29560-fcEM2ccDkbL2nhBuCrrZHw@public.gmane.org>
2012-10-07 20:46 ` Fw: " Junio C Hamano
2012-10-08 7:23 ` Ramkumar Ramachandra [this message]
2012-10-08 8:02 ` Fw: [git-users] " Jonathan Nieder
[not found] ` <20121008080208.GC19733-fcEM2ccDkbL2nhBuCrrZHw@public.gmane.org>
2012-10-08 15:39 ` Fw: " Junio C Hamano
[not found] ` <7v7gr1nfby.fsf-s2KvWo2KEQL18tm6hw+yZpy9Z0UEorGK@public.gmane.org>
2012-10-08 17:26 ` Junio C Hamano
2012-10-08 20:18 ` Fw: [git-users] " Jonathan Nieder
[not found] ` <20121008201816.GB7698-fcEM2ccDkbL2nhBuCrrZHw@public.gmane.org>
2012-10-08 21:38 ` Fw: " Junio C Hamano
2012-10-05 17:38 ` Konstantin Khomoutov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALkWK0nSxBsiE5_BZ67dPrwDRQSipL0LBR9Pf252iqL21HwZBA@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=flatworm@users.sourceforge.net \
--cc=fusionfile@gmail.com \
--cc=git-users@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=philippe.vaucher@gmail.com \
--cc=srabbelier@gmail.com \
--cc=tfnico@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).