Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] bugzilla: problem with "content-disposition" for patch files
Date: Sat, 10 Apr 2010 00:12:31 +0200	[thread overview]
Message-ID: <20100410001231.01b7d6f5@surf> (raw)
In-Reply-To: <hpnh5j$4bm$1@dough.gmane.org>

On Fri, 9 Apr 2010 15:29:55 +0000 (UTC)
Grant Edwards <grant.b.edwards@gmail.com> wrote:

> This may seem trivial, but it's getting to be pretty annoying.
> 
> When you click on a link to a patch file in bubzilla, the
> content-disposition is sent as "attachment".  This disables the
> ability of Firefox users to set a default action for that file type.
> 
> Can this be fixed?

I agree, this would be nice.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-04-09 22:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 15:29 [Buildroot] bugzilla: problem with "content-disposition" for patch files Grant Edwards
2010-04-09 22:12 ` Thomas Petazzoni [this message]
2010-04-10  0:47   ` Grant Edwards

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=20100410001231.01b7d6f5@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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