[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Advice for better SVN

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Thu, 24 Nov 2016 08:45:03 -0500

On Thu, Nov 24, 2016 at 6:19 AM, 蝌蚪 <25441950_at_qq.com> wrote:
> I'm a programmer who very love SVN.
> When I commit works through Internet, send files one by one always very
> slow.
> Why don't archive all files as a single Zip file, and send the only file to
> SVN server? (as like Git)
> Hope to help.
> Thanks.

Because Subversion doesn't normally send files, which could get very
bulky and very expensive to compare and verify on the other end. It
sends the *changes* in the files. This is much smaller, and safer if
there are "svn:keywords" enabled which may differ if checked out on a
server and checked out on a client.

Subversion, and most source control systems, does not keep complete
distinct copies of the files. They store the *changes* between file
revisions. including the original commit, and assemble the end file
from all the changes. It's one of the reasons anything that changes
history can be so dangerous.
Received on 2016-11-24 14:45:10 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.