All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Vales <jan@jvales.net>
To: git@vger.kernel.org
Subject: unexplained behavior/issue with git archive?
Date: Thu, 23 Jul 2015 17:23:49 +0200	[thread overview]
Message-ID: <55B10705.6090303@jvales.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

hi,
i seem to trigger behavior i do not understand with git archive.

I have this little 3 liner (vmdiff.sh):
#!/bin/bash
git diff --name-status "$2" "$3" > "$1.files"
git diff --name-only "$2" "$3" |xargs -d'\n' git archive -o "$1" "$3" --


For testing purpose, lets assume this call:
# ./vmdiff.sh latest.zip HEAD^1 HEAD

# cat latest.zip.files | wc -l
149021

# cat latest.zip.files | egrep "^D" | wc -l
159

# mkdir empty; cd empty; unzip latest.zip ; find * | wc -l
1090

My goal is to basically diff (parts of) filesystems against each other
and create an archive with all changed files + a file list to know what
files were deleted. (I currently do not care about the files
permissions+ownership, and it doesnt really matter in the current
problem. Also dont ask, why one would store a root-filesystem in git :)

What I do not understand: why does the zip file only contains 1090
files+dirs if the wc -l shows like 150k files and only like 159 were
deleted?
There should be like 149k files in that archive.

Also only the few files are all from "var" and none from etc or srv
where definitely files changed in too! (and show up in latest.zip.files)

Is there a limit of files git archive can process?

lg
Jan Vales
--
I only read plaintext emails.

Someone @ irc://irc.fsinf.at:6667/tuwien
webIRC: https://frost.fsinf.at/iris/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-07-23 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 15:23 Jan Vales [this message]
2015-07-23 15:59 ` unexplained behavior/issue with git archive? John Keeping
2015-07-23 17:21   ` Junio C Hamano

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=55B10705.6090303@jvales.net \
    --to=jan@jvales.net \
    --cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.