Hi Dale,
Well ehhh. I feel somewhat ashamed right now
When I followed your last instructions I stumbled upon a few hardlinks in
the tar-file from my original source. And, as I understood Git treats these
hardlinks as separate files. And yes, in the tar-file from Git I found a
few exact
From: peter ing...@gmail.com
When I followed your last instructions I stumbled upon a few hardlinks in
the tar-file from my original source. And, as I understood Git treats these
hardlinks as separate files. And yes, in the tar-file from Git I found a
few exact copy's for several
If you're willing to switch to soft links, many SCM tools (including git) will
handle those correctly. Plus tar will save the link rather than more copies of
the file.
wor...@alum.mit.edu wrote:
From: peter ing...@gmail.com
When I followed your last instructions I stumbled upon a few
Hi Paul,
Yep, I already modified my filesystem to soft-links. So now all goes well
with git.
Peter
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi Dale,
Well, I've been reading the articles you advised. And I've done some
extensive testing with various situations. But till now, all without the
result I would like.
My files turned out not to be 'contaminated' with large holes, so every
experiment with 'sparse options' (while copying,
Hi Martin,
Thanks, but my problem is not the difference between the size of the source
in the git-repository and the tar-file made from the same source. Obviously
tther will be differences depending on the compressing-algorithm used by
tar and git.
My problem is the difference between 2
javascript:
*Sent:* Monday, August 19, 2013 8:10 PM
*Subject:* [git-users] Strange effect when tar-ing a cloned repository
Hi All,
I've been trying to put my filesystem for a very small busybox-based
distro into a git-repository. And with succes. The only strange thing I can
not get my
did you already try a cleanup?
git gc
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, visit
Hi tombert,
No, not yet. At this moment I'm busy makeing a detailed list from all file-
directory-sizes before and after git-commit/git-checkout. Thereafter I'll
surely try 'git gc' !
Regards,
Peter
Op dinsdag 20 augustus 2013 09:28:23 UTC+2 schreef tombert:
did you already try a cleanup?
Hi Dale,
I've been running some tests to see if I could find the origin of my
size-difference. As it turned out, when examining the filesystem's size on
the target with 'su', this was about 10M bigger in case of the git-cloned
filesystem (I make a jffs2-file to flash the target, thereafter
Hi Dale,
Thanks for the explanation and tips. I'm gonna study the articles this
evening. So perhaps I can find the conclusive answer to my 'problem'.
Kindest regards,
Peter
Here's one explanation:
http://en.wikipedia.org/wiki/Sparse_files#Sparse_files_in_Unix
Also, read the du and cp
From: peter boudewijns ing...@gmail.com
I've been trying to put my filesystem for a very small busybox-based distro
into a git-repository. And with succes. The only strange thing I can not
get my head around is the following :
When making a compressed tarball from the files from the
- Original Message -
From: peter boudewijns
To: git-users@googlegroups.com
Sent: Monday, August 19, 2013 8:10 PM
Subject: [git-users] Strange effect when tar-ing a cloned repository
Hi All,
I've been trying to put my filesystem for a very small busybox-based distro
On 19 August 2013 21:10, peter boudewijns ing...@gmail.com wrote:
Hi All,
[...]
When making a compressed tarball from the files from the repository (after
clone/checkout) I get a very much larger tar.gz-file. Size goes up from 16M
to 21M (!?)
Not so strange. git is very good at
14 matches
Mail list logo
