From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-4.2 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id A50481F5AE for ; Tue, 20 Jul 2021 21:18:43 +0000 (UTC) Received: by mail-qk1-x72d.google.com with SMTP id j184so187276qkd.6 for ; Tue, 20 Jul 2021 14:18:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=qAZcguEuhARofp5/8wgSsYcyQTtzO1wwEHNX3xxkYa4=; b=AFX987gvoGRcvEXoVYEzjLTX4wcmiPJsFgziZYEU9zl2xBClD1QfddUXiHya5kDjME 4rt11t47JJ02AsxTUvP3K6GCaotSAI3LVNvX7gmCUGeFuy0EDAKgvAF60mO2tDfByINj oDwjd/WwUc0IJyf0kVH1HrrOoKDkYmCBLt+Io= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=qAZcguEuhARofp5/8wgSsYcyQTtzO1wwEHNX3xxkYa4=; b=PBLu56EtokF6wrMYI8Sf3FWRGkoAnkKpRMCbhDx5iC5u+I+qxpnpEqVfc1Vaks7tKY sbYQNff6k6j5/vFGkWF6EzrYkeiVYJsLrbnWRinFCvwOfCOB2Rg8adLIyn4mqbNbeT/0 mgWBx0Ju9f5wXkoM/liUO8i9l/OsMqsPc7HiNq+sIl1wBm6GbYEAm7OLIjgGktqtKAHF 2SORkzUnAVC8NTxa/WGjV/3icjLbwyJOuBg2y683igxO+ty/tykQJFacHsHp8ifP3fh9 vJnkzHHUGIaeHClf9anV6QXbgPbqb1Zp4yzwffA+CQ7fW3Kw1PPiJpDGvqSO5urk00Z8 Lk4w== X-Gm-Message-State: AOAM53337SbL03bewpivkzolsJQBQtdM/WysNz5HqU/zF+VZMl/figAu Rj83etBo139I4norqr/Mp+Vo2Q== X-Google-Smtp-Source: ABdhPJz9S7REU27QlmxBjzGfctJIfc4IAMJursR1b7TI+bRSqcq2KgMS7drOk+pucut5E9xDBNi5DQ== X-Received: by 2002:a05:620a:2224:: with SMTP id n4mr9771519qkh.424.1626815922578; Tue, 20 Jul 2021 14:18:42 -0700 (PDT) Received: from nitro.local ([89.36.78.230]) by smtp.gmail.com with ESMTPSA id a127sm9843984qkc.121.2021.07.20.14.18.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Jul 2021 14:18:42 -0700 (PDT) Date: Tue, 20 Jul 2021 17:18:40 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Restarting daemons on config file change Message-ID: <20210720211840.jl542wuyjh4ajowg@nitro.local> References: <20210719200318.wo4ydjonc3u3ibtu@nitro.local> <20210719204935.GA31835@dcvr> <20210720170019.p5d23tjb4v2mrekn@nitro.local> <20210720203433.GA28287@dcvr> <20210720204925.7xkk6ktihohxnfo3@nitro.local> <20210720210724.GA25323@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210720210724.GA25323@dcvr> List-Id: 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