From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Jakub Narebski <jnareb@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH/RESEND] gitweb: Fix snapshots requested via PATH_INFO
Date: Wed, 15 Apr 2009 13:29:27 +0200 [thread overview]
Message-ID: <cb7bb73a0904150429l7c9910aer847464add60ee345@mail.gmail.com> (raw)
In-Reply-To: <20090415100955.GA33221014@CIS.FU-Berlin.DE>
2009/4/15 Holger Weiß <holger@zedat.fu-berlin.de>:
> * Giuseppe Bilotta <giuseppe.bilotta@gmail.com> [2009-04-15 11:33]:
>> My gitweb over at http://git.oblomov.eu/ supports snapshots with
>> PATH_INFO just fine even without the need for this patch.
>
> Really? If I try to download a snapshot from your site, I get an empty
> tarball (and the server appends an additional ".tar.gz" suffix to the
> filename within the "Content-disposition" header). For example:
>
> $ wget -q -O - http://git.oblomov.eu/git/snapshot/v1.6.2.3.tar.gz | gzip -d | tar -t | wc -l
> 0
>
> That's the bug which is fixed by my patch.
This gets weirder and weirder. I'm seeing the same behaviour with your
patch. I think I busted something the upgrade I was running this
morning. Even git archive on the command line gives me an empty tar.
I have no idea what happened. I rebuilt and reinstalled git and now
it's working again, and I see the problem too, and yes your patch
fixes it.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2009-04-15 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090414104648.GA36554444@CIS.FU-Berlin.DE>
2009-04-15 6:40 ` [PATCH/RESEND] gitweb: Fix snapshots requested via PATH_INFO Junio C Hamano
2009-04-15 9:33 ` Giuseppe Bilotta
2009-04-15 10:09 ` Holger Weiß
2009-04-15 11:29 ` Giuseppe Bilotta [this message]
2009-04-15 17:34 ` Jakub Narebski
2009-04-20 9:52 ` Jakub Narebski
2009-04-20 10:41 ` 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=cb7bb73a0904150429l7c9910aer847464add60ee345@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
/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).