From: Chris Jones <chrisjones@spin.net.au>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Linux source tree size difference issue
Date: Fri, 17 May 2013 10:20:45 +1000 [thread overview]
Message-ID: <519577DD.3040204@spin.net.au> (raw)
I have cloned the Linux kernel source tree locally. It comes in at
approx. ~500MB. I have then created another git repository to push the
source to for my own work. I rsynced the tree locally to another
directory and now I am currently pushing it in to the new repository and
it's at 58% and is already at 525MB.
I can not understand the stark difference in source and directory size.
Running diff tells me both local source tree directories are exactly the
same.
Can anyone explain this in layman's terms?
--
Chris Jones
Founder and Lead Software Architect
Paradise Software
chrisjones@spin.net.au
next reply other threads:[~2013-05-17 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 0:20 Chris Jones [this message]
2013-05-17 19:44 ` Linux source tree size difference issue Roland Eggner
2013-05-18 2:00 ` Chris Jones
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=519577DD.3040204@spin.net.au \
--to=chrisjones@spin.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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