git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hommey <mh@glandium.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: rsync deprecated?
Date: Sat, 20 Dec 2008 09:15:11 +0100	[thread overview]
Message-ID: <20081220081511.GA28212@glandium.org> (raw)
In-Reply-To: <7vljuei2xw.fsf@gitster.siamese.dyndns.org>

On Wed, Dec 17, 2008 at 07:20:59PM -0800, Junio C Hamano wrote:
> 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.

Something that could well make this transport be maintained would be to
make it share code/internal API with the "local file transport".
Ideally, http, rsync and file could all share the same basis, and
ensuring the file transport to be functional would pretty much guarantee
all work.

Anyways, I'm not the right person to say that, as I've been failing to
deliver a beginning of such code for a year, now (damn, time goes too
fast).

Maybe libgit2 could be a good occasion to start some API like this,
though.

Mike

  parent reply	other threads:[~2008-12-20  8:13 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
2008-12-18  4:13   ` Markus Heidelberg
2008-12-20  8:15   ` Mike Hommey [this message]
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=20081220081511.GA28212@glandium.org \
    --to=mh@glandium.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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).