From: Maxime Devos <maximedevos@telenet.be>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
Nicolas Graves <ngraves@ngraves.fr>,
55618@debbugs.gnu.org
Subject: bug#55618: Allow patching from mummi issues
Date: Wed, 25 May 2022 16:21:32 +0200 [thread overview]
Message-ID: <eaea97237d725e18bea55f07486cc3580701bee2.camel@telenet.be> (raw)
In-Reply-To: <1f550c0c2958d79c46db5a2143b2af43e8f6b60d.camel@ist.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
Liliana Marie Prikler schreef op wo 25-05-2022 om 14:16 [+0200]:
> Am Mittwoch, dem 25.05.2022 um 13:06 +0200 schrieb Maxime Devos:
> > is text;charset=utf-8 actually valid?
> Not as far as I'm aware. The first part should be a proper MIME type,
> which ought to be registered by the IANA [1].
>
> > That page sets
> >
> > Content-Type text;charset=utf-8
> >
> > which apperently Guile's HTTP parser doesn't like.
> > Maybe it can be changed to text/patch (*) or text/diff (*) (or
> > text/plain) instead?
> >
> > (*) x- prefixes are deprecated
> As fate would have it, neither text/patch nor text/diff are registered
> over at the IANA [1]. As far as I'm aware, both (Linux/GNU)
> applications and browsers should understand the x- notation.
Neither is text/x-patch nor text/diff. I am not aware of any browser
that supports text/x-patch or text/x-diff (or text/patch for that
matter). If there are any applications that understand text/x-patch
but not text/patch, it should be easy to patch them to support the more
standard-ish text/patch (or text/diff).
(Registering them would be even better, but AFAICT no-one is interested
in writing a formal spec to submit.)
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2022-05-25 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 22:14 bug#55618: Allow patching from mummi issues Nicolas Graves via Bug reports for GNU Guix
2022-05-25 11:06 ` Maxime Devos
2022-05-25 12:06 ` Daniel Meißner via Bug reports for GNU Guix
2022-05-25 12:16 ` Liliana Marie Prikler
2022-05-25 14:21 ` Maxime Devos [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eaea97237d725e18bea55f07486cc3580701bee2.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55618@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
--cc=ngraves@ngraves.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).