From: Kay Sievers <kay.sievers@vrfy.org>
To: Martin Waitz <tali@admingilde.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>, git@vger.kernel.org
Subject: Re: gitweb / cg-export
Date: Thu, 17 Aug 2006 00:50:08 +0200 [thread overview]
Message-ID: <1155768608.3386.1.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <20060816224000.GE14459@admingilde.org>
On Thu, 2006-08-17 at 00:40 +0200, Martin Waitz wrote:
> hoi :)
>
> On Wed, Aug 16, 2006 at 04:23:05PM +0530, Aneesh Kumar K.V wrote:
> > @@ -1334,6 +1335,7 @@ sub git_shortlog_body {
> > "<td class=\"link\">" .
> > $cgi->a({-href => href(action=>"commit", hash=>$commit)}, "commit") . " | " .
> > $cgi->a({-href => href(action=>"commitdiff", hash=>$commit)}, "commitdiff") .
> > + " | " .$cgi->a({-href => "$my_uri/$project.tar.gz?" . esc_param("p=$project;a=snapshot;h=$commit")}, "snapshot") .
> > "</td>\n" .
> > "</tr>\n";
> > }
>
> Isn't there some other way to tell the webbroser how to name the file?
> I thought there is some HTML header to explicitly give one file name.
Something like in line 1923?
$cgi->header(-type => "$type", '-content-disposition' => "inline; filename=\"$save_as\"");
Kay
prev parent reply other threads:[~2006-08-16 22:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 0:16 gitweb / cg-export Toby White
2006-08-16 0:23 ` gitweb / cg-export - corrected patch Toby White
2006-08-16 9:54 ` gitweb / cg-export Jakub Narebski
2006-08-16 10:53 ` Aneesh Kumar K.V
2006-08-16 11:32 ` Aneesh Kumar K.V
2006-08-16 20:05 ` Fredrik Kuivinen
2006-08-16 18:01 ` Junio C Hamano
2006-08-17 6:29 ` gitweb: Support for snapshots in gitweb Aneesh Kumar K.V
2006-08-17 7:34 ` Junio C Hamano
2006-08-17 7:48 ` Aneesh Kumar
2006-08-17 9:49 ` Jakub Narebski
2006-08-16 22:40 ` gitweb / cg-export Martin Waitz
2006-08-16 22:50 ` Kay Sievers [this message]
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=1155768608.3386.1.camel@pim.off.vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
--cc=tali@admingilde.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).