public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: Linus Walleij <linusw@kernel.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: Wed, 14 Jan 2026 10:05:54 +0000	[thread overview]
Message-ID: <aWdqgqo7HzYo51u_@bogus> (raw)
In-Reply-To: <6f7ba903-147b-4779-bc0c-f1b2db67a98b@app.fastmail.com>

On Tue, Jan 13, 2026 at 10:52:08AM -0500, Konstantin Ryabitsev wrote:
> On Tue, Jan 13, 2026, at 08:03, Sudeep Holla wrote:
> > For me, it's most 1 week and I can see that it matches the expiry in the
> > token.
> 
> Apparently, this is because your project is set as "testing" in the Google
> Cloud Console. Tokens are issued for a week and then not auto-renewed. If
> you set your project as "Production", it will be issued for an hour and then
> auto-renewed (which matches my experience of never having to reauth).
> 
> I'm told to try this:
> Go to Google Cloud Console -> APIs & Services -> OAuth consent screen
> Check "Publishing status"
> If "Testing", click "Publish App" to move to production
> 
> You shouldn't need to do verification if the project is marked as
> internal/personal use. However, the project I'm using for this in my
> personal Gmail account is old and is grandfathered in a number of things, so
> I can't test this part out.
> 

It does not appear to be trivial. It seems that verification is required to
publish, and I am missing something that is preventing me from completing the
verification.

> I may create a Linux Foundation project so we can make this suck less at least for official maintainers.
> 

I see you have already done this, will give that a try and see. Thanks!

-- 
Regards,
Sudeep

  reply	other threads:[~2026-01-14 10:06 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 [this message]
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
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=aWdqgqo7HzYo51u_@bogus \
    --to=sudeep.holla@arm.com \
    --cc=linusw@kernel.org \
    --cc=mricon@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