public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <mricon@kernel.org>
To: users@kernel.org, tools@kernel.org
Subject: korgalore v0.6.0 now available
Date: Thu, 5 Mar 2026 13:18:33 -0500	[thread overview]
Message-ID: <20260305-stimulating-observant-coati-9e12da@lemur> (raw)

Hi, all:

Korgalore v0.6.0 is now available with a new subscribe command, default target
selection, and numerous bug fixes improving reliability across shallow clones,
remote errors, and GUI configuration handling.

New features
------------

kgl subscribe command group:

A new command group for managing mailing list subscriptions from the command
line. Instead of manually editing configuration files, you can now add and
manage subscriptions directly:

    kgl subscribe https://lore.kernel.org/lkml/
    kgl subscribe list
    kgl subscribe pause lkml
    kgl subscribe resume lkml
    kgl subscribe stop lkml

The "add" subcommand is the default, so "kgl subscribe URL" works as a
shorthand. Subscriptions are stored as individual conf.d/sub-{feed_key}.toml
files, keeping them separate from the main configuration.

track-subsystem --list:

A new -L/--list flag displays all tracked subsystems, showing the subsystem
name, configuration file path, and delivery details (target and labels) for
each tracked subsystem.

Enhancements
------------

Default target selection:

When --target/-t is not specified, commands now use the first configured target
instead of aborting with an error. This applies to yank, track add, subscribe
add, and track-subsystem, matching the existing GNOME applet behaviour which
already pre-selects the first target in its dropdown.

If no targets are defined in the configuration at all, kgl now aborts early
with a helpful message pointing to the configuration file.

Bug fixes
---------
- Non-lore feed URLs no longer create invalid directory paths; URLs are now
  sanitised by stripping the scheme and replacing special characters.
- track-subsystem no longer crashes when a lei query matches no messages.
- Cached is_empty_repo() check avoids redundant git subprocesses.
- Public-inbox commits that carry no message file (rm/purge commits) are now
  detected and treated as successful no-ops, instead of being retried
  indefinitely as delivery failures.
- Remote server errors (e.g. 503) are now logged as one-line warnings instead
  of full tracebacks, and a failure on one feed no longer aborts updates to the
  remaining feeds.
- New commit discovery no longer fails on shallow clones; the --ancestry-path
  flag has been removed from rev-list since public-inbox v2 epochs have linear
  history.
- Legacy migration no longer crashes when the git directory has no epoch repos
  (e.g. from an interrupted clone).
- Delivery state is now initialised immediately after the first feed clone,
  instead of wasting one full pull cycle.
- kgl pull no longer crashes after kgl track add due to a tuple size mismatch
  in tracked thread deliveries.
- Git error messages now include stderr output and exit codes.
- Shallow clone failure for dormant lists is handled by falling back to
  --depth=1 when the time-based shallow clone fails.
- GUI startup error for missing GTK dependencies is now shown before
  stdout/stderr are redirected, and pipx environments get a pipx-specific
  install command.
- GUI now automatically detects and reloads configuration files changed on
  disk before each sync cycle, preventing crashes from stale in-memory
  configuration.

Full changelog and documentation:

    https://korgalore.docs.kernel.org/

Source repository:

    https://git.kernel.org/pub/scm/utils/korgalore/korgalore.git

Install via pipx:

    pipx install korgalore

Thanks to the following people for suggestions and reports addressed in this
release:

- Ard Biesheuvel
- Borislav Petkov
- Dirk Behme
- Krzysztof Kozlowski
- Mark Brown
- Vlastimil Babka

-K

                 reply	other threads:[~2026-03-05 18:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260305-stimulating-observant-coati-9e12da@lemur \
    --to=mricon@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