From: Eli Zaretskii <eliz@gnu.org>
To: "Pierre Téchoueyres" <pierre.techoueyres@free.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Add support for base64url variant
Date: Wed, 22 May 2019 12:50:26 +0300 [thread overview]
Message-ID: <83zhne7r8d.fsf@gnu.org> (raw)
In-Reply-To: <3b0dc49f9831435178dc1b64d6a2f5c7@free.fr> (message from Pierre Téchoueyres on Wed, 22 May 2019 11:25:34 +0200)
> Date: Wed, 22 May 2019 11:25:34 +0200
> From: Pierre Téchoueyres <pierre.techoueyres@free.fr>
> Cc: emacs-devel@gnu.org
>
> Hello Eli,
> >
> > Thanks, but please avoid posting such large patches as long as you
> > don't have a copyright assignment for Emacs on file.
>
> I have already signed paperwork for TRAMP and, I think, for Emacs.
> But maybe there is something wrong with them ?
I do see the assignment for Tramp, but not for Emacs.
> If you can't find my previous assignment, then yes send me them back.
Will send off-list.
> I would like to have some discussion on how to improve some points :
> - Is adding parameter to existing functions the way to go or is it
> better to add new ones for base64url
I think an optional argument will be fine.
> - I would like to improve base64-decode* in a way it could detect the
> variant but actually don't know how to do that.
Maybe someone else will have an idea. Is such an algorithmic
detection described someplace?
> - The documentations is not really what I would like to see (and there
> my English is faulty)
Don't worry about that, we will polish it when the time comes. Thanks
for providing the documentation in the first place.
next prev parent reply other threads:[~2019-05-22 9:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 22:32 Add support for base64url variant Pierre Téchoueyres
2019-05-22 7:43 ` Eli Zaretskii
2019-05-22 9:25 ` Pierre Téchoueyres
2019-05-22 9:50 ` Eli Zaretskii [this message]
2019-05-23 17:51 ` Pierre Téchoueyres
2019-05-23 18:45 ` Noam Postavsky
2019-05-23 19:32 ` Pierre Téchoueyres
2019-05-23 18:58 ` Eli Zaretskii
2019-05-23 18:50 ` Eli Zaretskii
2019-05-23 19:37 ` Pierre Téchoueyres
2019-05-23 19:51 ` Eli Zaretskii
2019-05-27 20:30 ` Pierre Téchoueyres
2019-06-07 21:04 ` Pierre Téchoueyres
2019-06-08 5:52 ` Eli Zaretskii
2019-06-08 8:18 ` Eli Zaretskii
2019-06-11 18:36 ` Pierre Téchoueyres
2019-06-11 18:42 ` Eli Zaretskii
2019-06-11 18:47 ` Achim Gratz
2019-06-11 20:14 ` Richard Copley
2019-06-12 15:34 ` Eli Zaretskii
2019-06-12 6:50 ` Stefan Monnier
2019-06-12 19:24 ` Achim Gratz
2019-06-12 21:50 ` Stefan Monnier
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=83zhne7r8d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pierre.techoueyres@free.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 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).