From: James Bottomley <James.Bottomley@SteelEye.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] scsi updates for 2.6.12-rc2
Date: Fri, 15 Apr 2005 09:08:03 -0500 [thread overview]
Message-ID: <1113574084.5009.1.camel@mulgrave> (raw)
In-Reply-To: <20050415112556.GA6086@elf.ucw.cz>
On Fri, 2005-04-15 at 13:25 +0200, Pavel Machek wrote:
> Okay, so du -s is:
>
> root@amd:~# du -sh /tmp/delme.git/
> 109M /tmp/delme.git/
>
> Not as bad as I expected, but still quite a lot of data for few
> changes.
Erm, but that's why it's an rsync archive. You're supposed to have a
copy of the kernel archive already. The one at
rsync://www.kernel.org/pub/linux/kernel/people/torvalds/kernel-test.git
Then, the few additional files I have rsync across very fast.
Take a look at how git works: files, once added to the object tree by
sha1 hash stay there forever.
James
prev parent reply other threads:[~2005-04-15 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 1:27 [GIT PATCH] scsi updates for 2.6.12-rc2 James Bottomley
2005-04-15 10:36 ` Pavel Machek
2005-04-15 11:25 ` Pavel Machek
2005-04-15 14:08 ` James Bottomley [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1113574084.5009.1.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pavel@ucw.cz \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox