all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Maxime Devos <maximedevos@telenet.be>,
	Nicolas Graves <ngraves@ngraves.fr>,
	55618@debbugs.gnu.org
Subject: bug#55618: Allow patching from mummi issues
Date: Wed, 25 May 2022 14:16:17 +0200	[thread overview]
Message-ID: <1f550c0c2958d79c46db5a2143b2af43e8f6b60d.camel@ist.tugraz.at> (raw)
In-Reply-To: <92fba7b9bbb4fb5f7ac30cf6c49f833c12feb57f.camel@telenet.be>

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.

Cheers


[1] https://www.iana.org/assignments/media-types/media-types.xhtml




  parent reply	other threads:[~2022-05-25 12:26 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 [this message]
2022-05-25 14:21     ` Maxime Devos

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=1f550c0c2958d79c46db5a2143b2af43e8f6b60d.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=55618@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.