Date: Mon, 6 Dec 2004 01:57:22 +0000
From: Andrew Suffield <asuffield@debian.org>
To: gnu-arch-users@gnu.org
Subject: Re: [Gnu-arch-users] Arch Versus CVS Versus Subversoin
Message-ID: <20041206015722.GJ2799@suffields.me.uk>
Mail-Followup-To: gnu-arch-users@gnu.org
References: <20041205000613.PNEI7152.lakermmtao09.cox.net@nonerjsnum1tkq>
	<41B376B4.2060605@arbash-meinel.com>
	<20041206010853.GA2799@suffields.me.uk>
	<41B3B589.8010309@arbash-meinel.com>
Mime-Version: 1.0
In-Reply-To: <41B3B589.8010309@arbash-meinel.com>
User-Agent: Mutt/1.5.6+20040907i
Precedence: list
Content-Type: multipart/mixed; boundary="===============0805912583=="
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 3181
Lines: 105

--===============0805912583==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Do4IU1xF/9sod/r6"
Content-Disposition: inline


--Do4IU1xF/9sod/r6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Dec 05, 2004 at 07:27:37PM -0600, John A Meinel wrote:
> Andrew Suffield wrote:
> >On Sun, Dec 05, 2004 at 02:59:32PM -0600, John A Meinel wrote:
> >
> >>Arch does not support binary diff in the subversion sense.
> >
> >
> >Nonsense, it works just fine.
> >
>=20
> No. In subversion, if you have a binary file, and you make changes, it=20
> only stores the changes to the file. (something like xdelta). So if you=
=20
> have a binary file that is 100k long, and you append 10k to it, the=20
> changeset that is stored in the archive is only ~10k in size. (I think=20
> the same is true if you modify only 10k of the file.)
>=20
> However, with arch, if a file is declared binary and it is considered to=
=20
> be changed, then a completely new copy of the file is added to the=20
> repository. Actually, I just checked, and 2 new copies are added to the=
=20
> repository, the old version, and the new one.

Yes, arch supports binary diffs in exactly the same sense as subversion.

It doesn't do delta compression on them. That's irrelevant.

xdelta is not a diff. It's delta compression. That's even in the *name*.

> This is most definitely NOT what the original poster was meaning by=20
> "binary diff".

You mean they were out of their tree and using the wrong names for
things? You'll never get anywhere like that. "$foo diff" is an
operation which generates the input to "$foo patch", such that:

patch(A, diff(A, B)) =3D=3D B, where A and B are of type $foo

That's the definition.

> >Compression is not related in any way.
> >
>=20
> compression is not binary diff. True. But the reason people want binary=
=20
> diff is so that when you have your 10MB Word document, and you change 2=
=20
> lines in it, when you do the commit it doesn't have to upload 10MB of=20
> data.

No, the reason people want binary diffs is so that they can have
binary files stored in revision control. That's what it means and
that's what it does.

--=20
  .''`.  ** Debian GNU/Linux ** | Andrew Suffield
 : :' :  http://www.debian.org/ |
 `. `'                          |
   `-             -><-          |

--Do4IU1xF/9sod/r6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBs7yClpK98RSteX8RApGHAKCLA7YYJ2bIbocv6ef/55JsghFAWwCcC45m
q8V0SRqe4HZ8daZDbZr+EPs=
=R/d8
-----END PGP SIGNATURE-----

--Do4IU1xF/9sod/r6--


--===============0805912583==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/
--===============0805912583==--