From: Hamish Downer <dmishd@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Re: [sup-talk] Bug reading/writing contacts with \" in them
Date: Mon, 20 Jun 2011 23:45:43 +0100 [thread overview]
Message-ID: <1308609891-sup-2821@whisper> (raw)
In-Reply-To: <1295892863-sup-1896@midna.zekjur.net>
Excerpts from Michael Stapelberg's message of Mon Jan 24 18:20:13 +0000 2011:
> Excerpts from Ico's message of 2011-01-24 06:20:47 +0100:
> > The problem occurs when contacts have a certain combination of backslashes and
> > quotes in them.
> >
> > somename: \"Some, Name\" <somename@somedomain.com>
>
> Attached is a patch which fixes the issue. Input like "Rob, Post\" will first
> be turned into "Rob, Post\\" when initially escaping, but will then stay "Rob,
> Post\\" (no more exploding backslashes).
Another patch that slipped through the net. Now applied to next.
Hamish
--
Hamish Downer <hamish@foobacca.co.uk>
Web: http://www.foobacca.co.uk/
GPG: B7C48416
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2011-06-20 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1295845756-sup-308@pruts.nl>
2011-01-24 18:20 ` Michael Stapelberg
2011-06-20 22:45 ` Hamish Downer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1308609891-sup-2821@whisper \
--to=dmishd@gmail.com \
--cc=sup-devel@rubyforge.org \
/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