From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: gitster@pobox.com, Daniel Barkalow <barkalow@iabervon.org>,
git@vger.kernel.org
Subject: [PATCH 0/2] rsync support
Date: Fri, 28 Sep 2007 06:06:28 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709280602580.28395@racer.site> (raw)
Hi,
I worked too long on this... So here it is, a 2-patch series to readd the
rsync support.
One thing I did not do: fetch alternates. My rationale is this: just as
with HTTP, the rsync protocol does allow for having a different root than
the file system root. So, just as with HTTP, the alternates are likely to
break.
But hey, if somebody feels like it, there is a NEEDSWORK pointer from
which to start.
Ciao,
Dscho
next reply other threads:[~2007-09-28 5:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 5:06 Johannes Schindelin [this message]
2007-09-28 5:06 ` [PATCH 1/2] Introduce remove_dir_recursively() Johannes Schindelin
2007-09-28 9:05 ` Junio C Hamano
2007-09-28 12:35 ` Johannes Schindelin
2007-09-28 22:14 ` David Kastrup
2007-09-28 5:07 ` [PATCH 2/2] fetch/push: readd rsync support Johannes Schindelin
2007-09-28 5:20 ` Shawn O. Pearce
2007-09-28 12:22 ` Johannes Schindelin
2007-09-28 9:30 ` Junio C Hamano
2007-09-28 12:53 ` Johannes Schindelin
2007-09-28 15:28 ` [PATCH v2 0/2] rsync support, was Re: [PATCH 0/2] " Johannes Schindelin
2007-09-28 15:28 ` [PATCH v2 1/2] Introduce remove_dir_recursively() Johannes Schindelin
2007-09-28 15:29 ` [PATCH 2/2] fetch/push: readd rsync support Johannes Schindelin
2007-09-28 15:30 ` Johannes Schindelin
2007-09-28 21:20 ` Junio C Hamano
2007-09-28 22:48 ` Johannes Schindelin
2007-09-29 0:35 ` [PATCH v3 " Johannes Schindelin
2007-09-30 6:09 ` Junio C Hamano
2007-09-30 12:58 ` Johannes Schindelin
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=Pine.LNX.4.64.0709280602580.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.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).