From: Junio C Hamano <gitster@pobox.com>
To: markus.heidelberg@web.de
Cc: git@vger.kernel.org
Subject: Re: rsync deprecated?
Date: Wed, 17 Dec 2008 19:20:59 -0800 [thread overview]
Message-ID: <7vljuei2xw.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200812180041.10312.markus.heidelberg@web.de> (Markus Heidelberg's message of "Thu, 18 Dec 2008 00:41:10 +0100")
Markus Heidelberg <markus.heidelberg@web.de> writes:
> in the "Merging external work" section of the gitcore-tutorial it is
> stated that the rsync transport is deprecated. The description was added
> in commit 914328a (Update tutorial., 2005-08-30) together with the
> "deprecated" note. Having never heard/read this before and since this
> commit is quite old, I wonder if it is still the case or there was a
> solution for this problem.
Sorry, I do not quite understand what you perceive as "this problem".
It has been deprecated for too long a time. Maybe it is time to remove
the support, instead of carrying the deprecated command forever? Is that
the problem you are talking about?
I tend to agree that rsync transport way outlived its usefulness, and not
maintained at all. There may be unnoticed and undiagnosed bugs lurking,
but nobody knows about it because nobody uses it.
But the next release (1.6.1) won't be a good timing for removal. Perhaps
we can make an announcement now that it will be removed in a future major
update, and actually remove it in 1.7.0 or so.
next prev parent reply other threads:[~2008-12-18 3:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 23:41 rsync deprecated? Markus Heidelberg
2008-12-18 3:20 ` Junio C Hamano [this message]
2008-12-18 4:13 ` Markus Heidelberg
2008-12-20 8:15 ` Mike Hommey
2008-12-20 10:12 ` demerphq
2008-12-20 17:02 ` Miklos Vajna
2008-12-20 17:08 ` demerphq
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vljuei2xw.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=markus.heidelberg@web.de \
/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.
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 NNTP newsgroup(s).