From: Sudeep Holla <sudeep.holla@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Linus Walleij <linusw@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Sudeep Holla <sudeep.holla@kernel.org>,
tools@kernel.org, users@kernel.org
Subject: Re: korgalore v0.2 released with JMAP, IMAP, Maildir support
Date: Thu, 15 Jan 2026 17:27:02 +0000 [thread overview]
Message-ID: <aWkjZkI-sKqeM6ua@bogus> (raw)
In-Reply-To: <CAL_Jsq+f6A4zn6Ea-jK4YuP6RkY1syHEPwf-jGN3iPSOD5fL1w@mail.gmail.com>
On Tue, Jan 13, 2026 at 11:29:02AM -0600, Rob Herring wrote:
> On Tue, Jan 13, 2026 at 7:11 AM Sudeep Holla <sudeep.holla@arm.com> wrote:
> >
> > Hi Linus,
> >
> > Thanks for reporting this, I have been postponing it for a while.
> >
> > On Mon, Jan 12, 2026 at 08:52:45PM +0100, Linus Walleij wrote:
> > > On Sun, Jan 11, 2026 at 9:16 PM Konstantin Ryabitsev
> > > <konstantin@linuxfoundation.org> wrote:
> > >
> > > > > I would almost set this up to run as a cron job if it wasn't for the fact that
> > > > > the Googly API wants to reauthenticate every now and then. Other than
> > > > > that it is smooth as butter to work like this!
> > > >
> > > > I've not actually had to redo my gmail authentication again, but I do hear
> > > > that it's less smooth for others.
> > >
> > > I've had to do it twice, second time today.
> > >
> > > About that!
> > >
> >
> > For me, it's most 1 week and I can see that it matches the expiry in the
> > token.
> >
> > > What happens when the token expires is this:
> > >
> > > $ kgl pull
> > > (long splat like the one below)
> > >
> >
> > Yes I too get the same if the token has expired.
>
> In case you missed the earlier discussion, you can also just use IMAP
> with gmail and avoid all this. I just moved over to IMAP and it works
> fine. The only limitation I see is you can't set multiple labels on a
> message if you wanted to do that. I only used multiple labels for the
> UNREAD label, but that seems unnecessary for IMAP.
I had missed that discussion. I will give that(IMAP) a try too just to see
which works better for me. Thanks for pointing that out. I saw the discussion
in the thread now.
--
Regards,
Sudeep
next prev parent reply other threads:[~2026-01-15 17:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 15:21 korgalore v0.2 released with JMAP, IMAP, Maildir support Konstantin Ryabitsev
2025-12-17 17:50 ` Jason A. Donenfeld
2025-12-17 18:14 ` Konstantin Ryabitsev
2025-12-18 0:24 ` Linus Walleij
2025-12-18 1:57 ` Konstantin Ryabitsev
2025-12-18 2:42 ` Konstantin Ryabitsev
2025-12-18 18:51 ` Sudeep Holla
2025-12-18 20:47 ` Konstantin Ryabitsev
2025-12-18 22:41 ` Linus Walleij
2025-12-19 0:38 ` Konstantin Ryabitsev
2025-12-20 20:56 ` Linus Walleij
2025-12-22 15:50 ` Konstantin Ryabitsev
2025-12-22 22:33 ` Linus Walleij
2026-01-09 23:31 ` Linus Walleij
2026-01-11 20:15 ` Konstantin Ryabitsev
2026-01-12 19:52 ` Linus Walleij
2026-01-12 19:55 ` Bugspray Bot
2026-01-12 20:49 ` Konstantin Ryabitsev
2026-01-13 13:03 ` Sudeep Holla
2026-01-13 15:52 ` Konstantin Ryabitsev
2026-01-14 10:05 ` Sudeep Holla
2026-01-13 17:29 ` Rob Herring
2026-01-13 17:41 ` Konstantin Ryabitsev
2026-01-15 17:27 ` Sudeep Holla [this message]
2025-12-22 14:02 ` Linus Walleij
2025-12-22 15:11 ` Linus Walleij
2025-12-22 15:23 ` Konstantin Ryabitsev
2025-12-22 22:28 ` Linus Walleij
2025-12-19 18:54 ` Sudeep Holla
2025-12-19 19:20 ` Konstantin Ryabitsev
2025-12-18 13:40 ` Rob Herring
2025-12-18 13:51 ` Rob Herring
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=aWkjZkI-sKqeM6ua@bogus \
--to=sudeep.holla@arm.com \
--cc=konstantin@linuxfoundation.org \
--cc=linusw@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=tools@kernel.org \
--cc=users@kernel.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