git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: git@vger.kernel.org
Subject: Feature request: git-svn dcommit should send deltas upstream
Date: Tue, 26 Aug 2008 12:54:36 +0200	[thread overview]
Message-ID: <87myj0f3mb.fsf@mid.deneb.enyo.de> (raw)

Looking at my network traffic and the Perl code, it seems to me that
git-svn fails to create a diff (delta) before sending data to the
server.  As a result, a few changes in a multi-megabyte file lead to a
large upload (similar to the situation with CVS).  git-svn should be
able to compute this diff in all cases because it has got an up-to-date
copy of the current revision in the Subversion repository.

As far as I can tell, this can't be fixed with a one-liner; some handles
need to be passed down to the code that actually handles the upload.

             reply	other threads:[~2008-08-26 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 10:54 Florian Weimer [this message]
2008-08-29  8:23 ` Feature request: git-svn dcommit should send deltas upstream Eric Wong
2008-08-29 10:17   ` Florian Weimer
2008-08-31 16:14     ` Florian Weimer
2008-08-31 17:03       ` Junio C Hamano
2008-08-31 17:13         ` Florian Weimer
2008-09-01  3:41       ` Eric Wong
2008-09-01  8:09         ` Florian Weimer

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=87myj0f3mb.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=git@vger.kernel.org \
    /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).