Re: Are binary xdeltas only used if you use git-gc?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 3 Nov 2008, Thanassis Tsiodras wrote:

> Despair...
> 
> I just tested "git push --thin"...
> Doesn't work.
> 
> It still sends the complete object, not a tiny pack as it could (should).
> 
> But perhaps I now understand why:
> 
> I run git-gc on both the remote end and the working end (before
> changing anything,
> i.e. with both repos being in sync - "git pull" and "git push" report all OK).
> I then noticed that on the remote side, .git/objects/pack had one big pack file,
> but on the local one I have two .pack files...!
> 
> I proceeded to try (many combinations of params on) git-repack in a vain attempt
> to make my local repos also have one single .pack file (presumably, it
> should be able
> to exactly mirror the remote one, since it has the same objects inside
> it!). No way...

Please stop thinking that your repository layout has anything to do with 
what is actually transferred on a push.  It has not.

Here's a small test that you can do locally:

	mkdir repo_a
	mkdir repo_b
	cd repo_a
	git init
	seq 1000000 > data
	git add data
	git commit -m "initial commit"
	cd ../repo_b
	git init
	cd ../repo_a
	git push ../repo_b master:master

Here you should see a line that says:

	Writing objects: 100% (3/3), 2.01 MiB, done.

Therefore 2.1 MiB were transferred.  Now let's continue:

	echo "foo" >> data
	git add data
	git commit -m "second commit"
	git push ../repo_b master:master

You should get:

	Writing objects: 100% (3/3), 423 bytes, done.

And this means that you even don't need the --thin switch (which is 
wrong -- this has been broken before but that's another story) for the 
transfer to actually send only the difference and not the whole file 
again.  And note that none of those repositoryes actually contain any 
pack as everything is still loose objects.

> I'm at a loss as to why the two repos are having different "pack 
> representation" of the same objects

That's only because those objects entered each repositories in a 
different way.

> and why git-gc and git-repack fail 
> to create a single pack on my working side,

Maybe you have a .keep file in .git/objects/pack/ ?  If so delete it and 
run 'git repack -a -d'.

> but I'm guessing that this is why "git push --thin" fails to send 
> small xdeltas...

Not at all.

Please provide a complete log of your tests and maybe we could find 
something.


Nicolas
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux