Bug 349531 - Determining file type by glob for some filename masks
Summary: Determining file type by glob for some filename masks
Keywords:
Status: CLOSED DUPLICATE of bug 208714
Alias: None
Product: Bugzilla
Classification: Community
Component: Attachments/Requests
Version: 2.17
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-23 20:54 UTC by Matěj Cepl
Modified: 2013-06-24 02:52 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-02-06 15:36:20 UTC
Embargoed:


Attachments (Terms of Use)
test (21.65 KB, application/octet-stream)
2008-04-03 13:56 UTC, Matěj Cepl
no flags Details

Description Matěj Cepl 2007-10-23 20:54:26 UTC
Description of problem:
Being a bugmaster for the desktop two files we ask almost all reporters for
xorg-x11* components are /etc/X11/xorg.conf and /var/log/Xorg.0.log. Quite often
people don't call the attachments by this name, but they have different subtle
changes in the name of the attachment (like xorg-conf-hostname etc.) and in
almost cases, they don't select by hand, that the attachment is of the type
text/plain. The result of all this is that something like 80% of all attachments
are marked as application/octet-stream, which makes handling with them more
complicated (e.g., Firefox doesn't display them, but only downloads them).

Would it be possible to extend the mechanism for indicating type of attachments
so that default (of course, just default manually selected file types would not
be overriden) could be influenced by the list of file name masks which managers
of different components could extend. So for example, in my case I would say
that anything matching *Xorg*log* and *xorg*conf* would default to text/plain.

Does it make any sense?

Comment 1 Matěj Cepl 2008-02-06 15:36:20 UTC

*** This bug has been marked as a duplicate of 208714 ***

Comment 2 Matěj Cepl 2008-04-03 13:56:53 UTC
Created attachment 300250 [details]
test


Note You need to log in before you can comment on or make changes to this bug.