From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: Current state of GSSAPI support?
Date: Fri, 03 Feb 2017 10:49:38 +0100 [thread overview]
Message-ID: <8760kreh8t.fsf@koldfront.dk> (raw)
In-Reply-To: <CADtN0W+YC=doGJajTMHoTqiXVQWuktsyW6EZC17LYnHD8hUfTQ@mail.gmail.com>
Elias writes:
> Do you (or anyone else) have any opinion on the choice to use modules
> here? If I complete this, is there a chance that this be accepted for
> merge, or would the existence of the module make things more complicated?
I haven't the foggiest unfortunately, I don't have the bandwidth to
follow the Emacs development - maybe asking on the emacs-devel list is
more likely to give you some informed opinions?
Best regards,
Adam
--
"Do I really want to set this in Denmark?" Adam Sjøgren
asjo@koldfront.dk
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2017-02-03 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 3:19 Elias Mårtenson
2017-02-03 4:26 ` Jochen Hein
2017-02-03 7:35 ` Adam Sjøgren
2017-02-03 7:48 ` Elias Mårtenson
2017-02-03 9:49 ` Adam Sjøgren [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=8760kreh8t.fsf@koldfront.dk \
--to=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.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;
as well as URLs for NNTP newsgroup(s).