git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
Date: Wed, 20 Apr 2005 18:56:11 +0200	[thread overview]
Message-ID: <dnbr898k0k.fsf@magla.zg.iskon.hr> (raw)
In-Reply-To: <Pine.LNX.4.58.0504191525290.2274@ppc970.osdl.org> (Linus Torvalds's message of "Tue, 19 Apr 2005 15:38:17 -0700 (PDT)")

Linus Torvalds <torvalds@osdl.org> 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

  parent reply	other threads:[~2005-04-20 16:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19  4:39 [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2 Greg KH
2005-04-19 18:58 ` Greg KH
2005-04-19 19:40   ` Linus Torvalds
2005-04-19 19:47     ` Greg KH
2005-04-19 20:20       ` Linus Torvalds
2005-04-19 21:40         ` Greg KH
2005-04-19 22:00           ` Linus Torvalds
2005-04-19 22:27             ` Daniel Jacobowitz
2005-04-19 22:33               ` Greg KH
2005-04-19 23:04                 ` Kenneth Johansson
2005-04-19 22:47               ` Linus Torvalds
2005-04-19 22:29             ` Martin Schlemmer
2005-04-19 22:43               ` Linus Torvalds
2005-04-19 23:11                 ` Martin Schlemmer
2005-04-20  0:01                 ` Jan-Benedict Glaw
2005-04-19 22:52             ` Lars Fenneberg
2005-04-19 22:39         ` Petr Baudis
2005-04-19 22:49           ` Linus Torvalds
2005-04-19 22:19     ` Steven Cole
2005-04-19 22:26       ` Petr Baudis
2005-04-19 22:45         ` Junio C Hamano
2005-04-19 22:58           ` Petr Baudis
2005-04-19 22:38       ` Linus Torvalds
2005-04-19 23:02         ` Petr Baudis
2005-04-19 23:04         ` Steven Cole
2005-04-19 23:16           ` Petr Baudis
2005-04-19 23:38           ` Linus Torvalds
2005-04-19 23:41             ` Steven Cole
2005-04-20 16:56         ` Zlatko Calusic [this message]
2005-04-20 17:15           ` Linus Torvalds

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dnbr898k0k.fsf@magla.zg.iskon.hr \
    --to=zlatko.calusic@iskon.hr \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).