Re: Restarting daemons on config file change

[Konstantin Ryabitsev <konstantin@linuxfoundation.org>]

On Tue, Jul 20, 2021 at 09:07:24PM +0000, Eric Wong wrote:
> > I figured as much, but we do want to set extra keys *and* write the config in
> > a certain order (e.g. prioritizing some sources over others by listing them
> > first). I currently do this via a list-id globbing match (e.g.
> > --listid-priority=*.linux.dev,*.kernel.org,*).
> 
> Ah, that gets tricky, since git-config doesn't seem to provide a
> mechanism for ordering.  Not sure, perhaps serializing -init
> invocations somehow is the way to go?  I'm not sure how to
> expose that ordering, though...

Serializing wouldn't necessarily help, as a list may be added to an existing
archive collection at some later point, and we don't necessarily want it at
the bottom.

Another thought would be to give a "rank" ("weight"/"priority") configuration
option that you can check before falling back to the listed order. E.g.:

[publicinbox "dkim-mangling"]
  listid=dkim-mangling.list.example.org
  rank=10

[publicinbox "dkim-respecting"]
  listid=dkim-respecting.list.example.net
  rank=1

This way higher-ranking entries will win when returning aggregating threads,
so we're less likely to see results from known dkim-mangling sources.

-K