Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: decklin@red-bean.com (Decklin Foster)
Subject: [sup-talk] "X-" headers
Date: Sun, 26 Oct 2008 14:41:55 -0400	[thread overview]
Message-ID: <1225046068-sup-1321@gillespie.rupamsunyata.org> (raw)

I've noticed sup strips X-Foo: from mails during editing (or indeed, any
header that isn't recognized in mbox.rb). I think it would be better to
just ignore and pass them on (as they are officially okay in emails whereas
random unknown non "X-" headers are not). What do people think?

(I use X-Tags: for blogging, myself. I also used to have a joke X-Windows:
header.)

I've pushed a change to fix it to Gitorious:
http://gitorious.org/projects/sup/repos/decklins-clone/commits/aa1b6846c33b44dfd723ad9657448e45e7a2a143
(I moved up the special-case X- stuff so this doesn't interfere with it. Might
not actually be necessary.)

William, for future patch submissions, is it cool to just say "hey, I
commited something", and then you can pull it if desired? Or should I attach
the patch here for discussion?
-- 
things change.
decklin at red-bean.com


             reply	other threads:[~2008-10-26 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26 18:41 Decklin Foster [this message]
2008-10-28  2:15 ` William Morgan
2008-10-31 16:56   ` Marc Hartstein

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=1225046068-sup-1321@gillespie.rupamsunyata.org \
    --to=decklin@red-bean.com \
    /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