From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: schwab@suse.de, fitzsim@fitzsim.org, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: emacs-25 b6b47AF: Properly encode/decode base64Binary data in SOAP
Date: Mon, 14 Mar 2016 20:52:35 +0200 [thread overview]
Message-ID: <8360wodh8s.fsf@gnu.org> (raw)
In-Reply-To: <87a8m0j3w6.fsf@gmx.de> (message from Michael Albinus on Mon, 14 Mar 2016 19:44:25 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: schwab@suse.de, fitzsim@fitzsim.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
> Date: Mon, 14 Mar 2016 19:44:25 +0100
>
> > Does debbugs know the value is a text string?
>
> debbugs.el knows for every attribute, whether it is a string or
> something else. There're not so many attributes, see `debbugs-get-status'.
If debbugs.el knows it is a text string, then debbugs.el could decode
it (provided that soap-client.el gives you a unibyte undecoded string
that came out of base64 decoding).
next prev parent reply other threads:[~2016-03-14 18:52 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160106200404.17375.71733@vcs.savannah.gnu.org>
[not found] ` <E1aGuJQ-0004Wv-Lz@vcs.savannah.gnu.org>
2016-03-10 1:03 ` emacs-25 b6b47af: Properly encode/decode base64Binary data in SOAP Thomas Fitzsimmons
2016-03-10 9:30 ` Andreas Schwab
2016-03-11 3:29 ` emacs-25 b6b47AF: " Thomas Fitzsimmons
2016-03-11 8:35 ` Andreas Schwab
2016-03-11 13:49 ` Alex Harsanyi
2016-03-11 14:09 ` Andreas Schwab
2016-03-11 16:48 ` Stefan Monnier
2016-03-11 16:59 ` Andreas Schwab
2016-03-11 22:27 ` Stefan Monnier
2016-03-13 3:52 ` Thomas Fitzsimmons
2016-03-13 15:15 ` Stefan Monnier
2016-03-13 18:09 ` Thomas Fitzsimmons
2016-03-13 16:02 ` Eli Zaretskii
2016-03-13 17:57 ` Thomas Fitzsimmons
2016-03-13 18:30 ` Eli Zaretskii
2016-03-13 19:54 ` Thomas Fitzsimmons
2016-03-13 20:19 ` Eli Zaretskii
2016-03-13 21:17 ` Thomas Fitzsimmons
2016-03-14 3:30 ` Eli Zaretskii
2016-03-14 8:49 ` Andreas Schwab
2016-03-14 9:15 ` Michael Albinus
2016-03-14 11:56 ` Stefan Monnier
2016-03-14 12:18 ` Alex Harsanyi
2016-03-14 11:58 ` Alex Harsanyi
2016-03-14 12:38 ` Michael Albinus
2016-03-14 13:18 ` Alex Harsanyi
2016-03-14 13:30 ` Michael Albinus
2016-03-14 13:26 ` Stefan Monnier
2016-03-14 14:12 ` Michael Albinus
2016-03-14 14:58 ` Thomas Fitzsimmons
2016-03-14 15:56 ` Michael Albinus
2016-03-14 17:58 ` Eli Zaretskii
2016-03-15 1:56 ` Thomas Fitzsimmons
2016-03-15 7:45 ` Andreas Schwab
2016-03-15 7:57 ` Michael Albinus
2016-03-15 7:49 ` Andreas Schwab
2016-03-15 8:08 ` Michael Albinus
2016-03-15 14:39 ` Thomas Fitzsimmons
2016-03-15 15:04 ` Michael Albinus
2016-03-17 14:23 ` Thomas Fitzsimmons
2016-03-17 15:39 ` Thomas Fitzsimmons
2016-03-17 19:24 ` Michael Albinus
2016-03-17 15:46 ` Stefan Monnier
2016-03-15 17:39 ` Eli Zaretskii
2016-03-14 17:53 ` Eli Zaretskii
2016-03-14 18:47 ` Michael Albinus
2016-03-14 18:57 ` Eli Zaretskii
2016-03-14 17:49 ` Eli Zaretskii
2016-03-14 18:44 ` Michael Albinus
2016-03-14 18:52 ` Eli Zaretskii [this message]
2016-03-14 19:05 ` Michael Albinus
2016-03-14 9:23 ` Thomas Fitzsimmons
2016-03-14 9:58 ` Andreas Schwab
2016-03-14 8:02 ` Michael Albinus
2016-03-14 12:39 ` Stefan Monnier
2016-03-14 17:55 ` Eli Zaretskii
2016-03-14 17:48 ` Eli Zaretskii
2016-03-14 18:42 ` Michael Albinus
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8360wodh8s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fitzsim@fitzsim.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@suse.de \
/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/emacs.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).