From: bm@bjornmichelsen.com (Bjorn Michelsen)
Subject: [sup-talk] Saving status of merged threads with '#' on next branch
Date: Wed, 15 Apr 2009 17:58:03 +0200 [thread overview]
Message-ID: <1239810733-sup-5572@snowstorm> (raw)
In-Reply-To: <1239299963-sup-5933@entry>
Excerpts from William Morgan's message of to. april 09 20:02:08 +0200 2009:
> > I'm a bit lost as to where I should begin troubleshooting, so I'm
> > wondering if someone else have had the same problem?
>
> It's a known problem. I'm not sure why it isn't saved. If you want to
> start investigating, ThreadSet#join_threads in lib/sup/threads.rb is the
> joining code. Maybe the call to Message#add_ref is wrong somehow.
Thanks for clearing that up, as well as the additional information
regarding where to start looking.
> I'm also curious about your From: line, which is RFC2047-encoded but
> with the "UNKNOWN" charset. What produces that? Surely not Sup!
I haven't replied earlier because I've been trying to figure out what
causes the strange From: address.
locale outputs the following:
LANG=nb_NO.UTF-8
LC_CTYPE=nb_NO.UTF-8
LC_NUMERIC="nb_NO.UTF-8"
LC_TIME="nb_NO.UTF-8"
LC_COLLATE="nb_NO.UTF-8"
LC_MONETARY="nb_NO.UTF-8"
LC_MESSAGES=en_US.UTF-8
LC_PAPER="nb_NO.UTF-8"
LC_NAME="nb_NO.UTF-8"
LC_ADDRESS="nb_NO.UTF-8"
LC_TELEPHONE="nb_NO.UTF-8"
LC_MEASUREMENT="nb_NO.UTF-8"
LC_IDENTIFICATION="nb_NO.UTF-8"
LC_ALL=
And Vim is saying that all files related to sup is encoded as utf8.
So, at the moment I don't know why this is happening. Maybe someone
using special characters can let me in on their secret?
--
Mvh.
Bj?rn Michelsen
MOB: +47 934 55 474
next prev parent reply other threads:[~2009-04-15 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 20:44 =?UNKNOWN?Q?Bj=C3=B8rn?= Michelsen
2009-04-09 15:39 ` Mark Alexander
2009-04-09 18:02 ` William Morgan
2009-04-15 15:58 ` Bjorn Michelsen [this message]
2009-04-15 17:33 ` William Morgan
2009-04-16 9:53 ` Bjorn Michelsen
2009-04-21 13:28 ` William Morgan
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=1239810733-sup-5572@snowstorm \
--to=bm@bjornmichelsen.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