Re: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2

Linus Torvalds [off-list ref] writes:

Real merges have no patches taking place _anywhere_. And they take about 
half a second. Doing an "update" of your tree should _literally_ boil down 
to

	#
	# "repo" needs to point to the repo we update from
	#
	rsync -avz --ignore-existing $repo/objects/. .git/objects/.

I see this -avz incantation mentioned everytime when rsync is
involved. But, is the -z part (compression) really necessary knowing
that we're dealing with an already compressed tree? Doesn't it put
additional strain on the rsync server without any benefit in this
case?

Or I might be too ignorant and not understand some internals well, but
then... I would like to know the reason. :)

Regards,
-- 
Zlatko

On Wed, 20 Apr 2005, Zlatko Calusic wrote:

I see this -avz incantation mentioned everytime when rsync is
involved. But, is the -z part (compression) really necessary knowing
that we're dealing with an already compressed tree? Doesn't it put
additional strain on the rsync server without any benefit in this
case?

Or I might be too ignorant and not understand some internals well, but
then... I would like to know the reason. :)

I'm not a big rsync user, so I just copied the examples of others.

You're right, for git, you should not use compression for files (I don't 
know if rsync compresses the directory listings by default, I assume it 
does). 

		Linus