From: Rogan Dawes <lists@dawes.za.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: git-archive loses path info when opened with Winzip?
Date: Mon, 31 Mar 2008 13:59:17 +0200 [thread overview]
Message-ID: <47F0D215.1060700@dawes.za.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
Hi folks,
I have noticed something strange with "git-archive"-created tarballs. It
seems that Winzip has trouble parsing the paths for certain files correctly.
The symptom is that Winzip shows some files as having been created at
the "top level" of the zip, without any path at all, while the rest of
the files are within their correct directory structure.
I have attached a screenshot of a gitweb-created snapshot opened in
Winzip 9.0 SR1 (build 6224), but it apparently happens in other (more
recent) versions of Winzip as well.
The tarball in question is at:
<http://dawes.za.net/gitweb.cgi?p=rogan/webscarab/webscarab.git;a=snapshot;h=7ee920dad6b41987f692017dbd9b85259e7a8fe5>
(It's a 2.7MB file). And yes, it happens when git-archive is called
directly, not just via gitweb.cgi.
Regular GNU tar (cygwin) shows the correct path info: (for example)
0 $ tar -tvzf /tmp/webscarab.tar.gz | grep AbstractTreeTableModel
-rw-rw-r-- root/root 2311 2008-03-08 22:35
rogan/webscarab/webscarab.git/src/org/owasp/webscarab/util/swing/treetable/AbstractTreeTableModel.java
0 $
The version of git on the server is:
> [rdawes@lucas rdawes]$ which git
> /home/rdawes/bin/git
> [rdawes@lucas rdawes]$ git --version
> git version 1.5.5.rc1.6.g5cc8f
Any ideas what may be going wrong here? Note that it doesn't seem to
happen when generating a ZIP using git-archive, but only when generating
tarballs.
Regards,
Rogan
[-- Attachment #2: webscarab_winzip.png --]
[-- Type: image/png, Size: 67147 bytes --]
next reply other threads:[~2008-03-31 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 11:59 Rogan Dawes [this message]
2008-03-31 19:47 ` git-archive loses path info when opened with Winzip? René Scharfe
2008-03-31 20:09 ` Rogan Dawes
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=47F0D215.1060700@dawes.za.net \
--to=lists@dawes.za.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 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 NNTP newsgroup(s).