From: Jochen Hein/Jochen Kellner <jochen@jochen.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: allow GSSAPI for imap access
Date: Sun, 20 Mar 2016 20:11:26 +0100 [thread overview]
Message-ID: <83d1qpc6ch.fsf@jochen.org> (raw)
In-Reply-To: <877fhyhi6l.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 21 Feb 2016 14:10:42 +1100")
Hello Lars,
Lars Ingebrigtsen <larsi@gnus.org> writes:
> "Hein, Jochen" <jochen@jochen.org> writes:
>
>> I'm unsure - I have translator papers on file, and maybe some from the
>> ninetys.
>
> I've looked at the copyright assignment file, and there doesn't seem to
> be anything that covers Emacs.
>
>> Shall I just file papers?
>
> Yes, please do.
Now my papers are on file. Anything else I should do?
Jochen
--
The only problem with troubleshooting is that the trouble shoots back.
prev parent reply other threads:[~2016-03-20 19:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 16:07 Jochen Hein
2016-02-14 16:07 ` [PATCH 1/4] open-gssapi-stream: remove parameter user Jochen Hein
2016-02-14 16:07 ` [PATCH 2/4] network-stream: allow type gssapi Jochen Hein
2016-02-14 16:07 ` [PATCH 3/4] nnimap: handle imap connections with type 'gssapi Jochen Hein
2016-02-14 16:07 ` [PATCH 4/4] update nnimap documentation for gssapi connections Jochen Hein
2016-02-15 7:59 ` allow GSSAPI for imap access Lars Ingebrigtsen
2016-02-15 14:35 ` Adam Sjøgren
2016-02-15 16:39 ` Jochen Hein
2016-02-15 17:29 ` Adam Sjøgren
2016-02-15 18:31 ` Jochen Hein
2016-02-15 18:56 ` Adam Sjøgren
2016-02-15 19:58 ` Jochen Hein
2016-02-22 7:27 ` Adam Sjøgren
2016-02-22 18:41 ` Jochen Hein
2016-02-23 12:52 ` Adam Sjøgren
2016-02-15 14:38 ` Hein, Jochen
2016-02-15 14:46 ` Lars Ingebrigtsen
2016-02-16 5:57 ` Lars Ingebrigtsen
2016-02-16 9:21 ` Hein, Jochen
2016-02-21 3:10 ` Lars Ingebrigtsen
2016-03-20 19:11 ` Jochen Hein/Jochen Kellner [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=83d1qpc6ch.fsf@jochen.org \
--to=jochen@jochen.org \
--cc=ding@gnus.org \
--cc=larsi@gnus.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).