From: Martin Steigerwald <martin@lichtvoll.de>
To: Lars Ingebrigtsen <larsi@gnus.org>, kde-pim@kde.org
Cc: groot@kde.org, oub@mat.ucm.es, rms@gnu.org, kde-pim@kde.org,
emacs-devel@gnu.org
Subject: Re: Kmail: Gmail (less secure apps) advice for GNU emacs developers.
Date: Sat, 15 Aug 2020 11:14:29 +0200 [thread overview]
Message-ID: <1626223.fKZIis3IFj@merkaba> (raw)
In-Reply-To: <E1k6nzq-0007PQ-HY@fencepost.gnu.org>
Hi Richard.
Richard Stallman - 15.08.20, 06:40:46 CEST:
[…]
> > Like I've said I don't know how many times now, I'm not working on
> > this problem at all. You'll have to find somebody that can
> > register these developer accounts (legally) on behalf of the FSF,
> > and have them go through the review etc.
>
> I think we are miscommunicating. Perhaps in two ways.
You are missing context. See below.
> You said you didn't want to do the work to follow what Google
> said to do. I understand. But now we are talking about following
> the Kmail method. I don't know what either one actually is, though.
> How similar are those two?
Richard, Adriaan de Groot described the process what Daniel did for
KMail. You have not (yet) been on cc. Daniel basically did what Google
asked him to do:
https://mail.kde.org/pipermail/kde-pim/2020-August/046550.html
Blog posts of Adrian referenced in there:
Akonadi / KMail and Google accounts
https://euroquis.nl/kde/2020/01/13/google.html
Akonadi / KMail and Google accounts resolved!
https://euroquis.nl/kde/2020/05/12/google.html
Also review this blog post by Dan himself:
Kontact and Google Integration Issues
https://www.dvratil.cz/2019/08/kontact-google-integration-issue/
As I have no interest whatsoever to use Google products like GMail, I
have no intention to answer any further questions. I just thought I
clear up the misunderstanding.
Best,
--
Martin
next prev parent reply other threads:[~2020-08-15 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87o8njdlvs.fsf@mat.ucm.es>
[not found] ` <1897936.H7q943mS67@merkaba>
[not found] ` <5532801.MhkbZ0Pkbq@twilight>
2020-08-10 16:20 ` Kmail: Gmail (less secure apps) advice for GNU emacs developers Uwe Brauer
2020-08-10 16:46 ` Allan Sandfeld Jensen
2020-08-10 22:37 ` Stefan Monnier
2020-08-11 18:15 ` Uwe Brauer
2020-08-11 18:53 ` Stefan Monnier
2020-08-13 6:57 ` Uwe Brauer
2020-08-13 8:13 ` Robert Pluim
[not found] ` <21978174.sr7ieKrsik@beastie.bionicmutton.org>
2020-08-13 8:49 ` Uwe Brauer
2020-08-14 2:55 ` Richard Stallman
2020-08-14 4:25 ` 황병희
2020-08-14 10:16 ` Lars Ingebrigtsen
2020-08-15 4:40 ` Richard Stallman
2020-08-15 9:14 ` Martin Steigerwald [this message]
2020-08-15 9:20 ` Martin Steigerwald
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=1626223.fKZIis3IFj@merkaba \
--to=martin@lichtvoll.de \
--cc=emacs-devel@gnu.org \
--cc=groot@kde.org \
--cc=kde-pim@kde.org \
--cc=larsi@gnus.org \
--cc=oub@mat.ucm.es \
--cc=rms@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.