From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: Linus Walleij <linusw@kernel.org>, tools@kernel.org, users@kernel.org
Subject: Re: korgalore v0.2 released with JMAP, IMAP, Maildir support
Date: Fri, 19 Dec 2025 14:20:31 -0500 [thread overview]
Message-ID: <20251219-melodic-unbiased-tarsier-e4f9bb@lemur> (raw)
In-Reply-To: <aUWfbRAHjNI-lNOz@bogus>
On Fri, Dec 19, 2025 at 06:54:37PM +0000, Sudeep Holla wrote:
> > Oh no, this is what happens when I don't check adding new feeds after a major
> > refactor. I think it's working correctly now in 0.2.2 -- please check!
> >
> Thanks for the fix. I can see the pull doesn't give any errors but it doesn't
> seem to push anything to my gmail label.
On the first run, or on all subsequent runs? It only initializes the feed on
the first run, but the ones after that should result in mails being imported.
I see the following in your log output for pull
> debug: Connecting to Gmail service for linux
> debug: Running git command: git -C /.local/share/korgalore/lkml/git/18.git show ba387a13f1918fbd9bf2ccdea11d5184c6c1774f:m
> debug: -> Re: [PATCH v5 02/36] compiler-context-analysis: Add infrastructure for Context Analysis with Clang
> [...]
> Pull complete with updates:
> lkml: 1
So, that message was for sure uploaded to your gmail account.
Since it's LKML, it gets upwards of a few thousand messages a day, so you will
definitely notice if it's working or not after a few "pull" runs. :)
> I have also added my config file with feed urls at the end. I have chosen
> lists that I have not subscribe to in order to avoid any confusion.
That's an important thing to remember with Gmail -- if you already have that
message *somewhere* in your inbox, Gmail will quietly drop the import. So, if
you don't see it in your LINUX/LKML label, that means you probably already had
that message.
Let me know if that helps!
-K
next prev parent reply other threads:[~2025-12-19 19:20 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
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 [this message]
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=20251219-melodic-unbiased-tarsier-e4f9bb@lemur \
--to=konstantin@linuxfoundation.org \
--cc=linusw@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