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=-3.7 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-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (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 016D81F8C6 for ; Tue, 29 Jun 2021 12:56:29 +0000 (UTC) Received: by mail-qt1-x833.google.com with SMTP id c13so318267qtb.12 for ; Tue, 29 Jun 2021 05:56:29 -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=DdsOxGwaOqftrKQGueIeYE0Z8rkjA1fmwWUGdmNfMfM=; b=aOclCZgM3+e4tNez/mO7BcY4sv75xMgZbls0TMgIQLPDtvSOJKfTn7RJ+bio1i2hz4 RLaaHX1rwCIso0fmzfcHKfyrcOwN/wFO9heEUGc3E4pBVeH8aQsw+vOZa/+ziWPlxRFh 2Ggyn2bsYOdlVBugzz0z54Gc/m5a/2nrXVoj0= 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=DdsOxGwaOqftrKQGueIeYE0Z8rkjA1fmwWUGdmNfMfM=; b=PkTw8hKltTkBzaZxU1G1fxarv8BJRdiWBm+/Ps9s3SXrfjqSdABSXxL/mJKO3ElLAw Lhb6Gfr9vudqFNah7C1MWpsZF/uulkPvmG8eaDhjf8CrRmLuNlWzBm5/hJ/QEgE54yaJ t30+hUMiJeRAMZvDqy9yW2OkdPemEj2rYKBS3muyflqKLX4jLnXFg8+rGEKt+LCjW8zb 3Oyu1VeMgApVMgBx3i/IEAPY++2OAJkWRcF9mRdlHRv9xfLndY5O+btnfSg9YOsYlVc7 CYkrV9PqVRXh3lOJrS7elK0sg/B6KkTbehvYGdHW0X8cABYINvUl0ToShfEbYddnuP01 k7OQ== X-Gm-Message-State: AOAM5339TEi6caiBnhfuy62dx3eanCzafGDGVV1TQgO99fKtAn0vW0p+ eQt6vyK/5Ro2gL3HbBvcGu71J4EfnrWm3w== X-Google-Smtp-Source: ABdhPJzactZXMj0bf6R94VahU+WW0ZqpAG2X5XUNsBSfKp6rij4RK8OBTcAA9i/8fgz8R2wsLIuEdQ== X-Received: by 2002:ac8:149a:: with SMTP id l26mr26174038qtj.297.1624971388750; Tue, 29 Jun 2021 05:56:28 -0700 (PDT) Received: from nitro.local ([89.36.78.230]) by smtp.gmail.com with ESMTPSA id m189sm11854842qkd.107.2021.06.29.05.56.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Jun 2021 05:56:28 -0700 (PDT) Date: Tue, 29 Jun 2021 08:56:26 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Recording archiver origins in git Message-ID: <20210629125626.c5e6ianh6yilbakp@nitro.local> References: <20210628212610.zbexle2b2uvux2sd@nitro.local> <20210628221236.GA25399@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210628221236.GA25399@dcvr> List-Id: On Mon, Jun 28, 2021 at 10:12:36PM +0000, Eric Wong wrote: Hope you're finding ways of staying cool and sane. It's hot here on the East coast, but a) we're used to it, and b) it's not yikes degrees. > > Imaginary code snippet: > > > > $ git show refs/meta/origins:i > > [metadata] > > source = smtp > > Is "source" necessary? It seems like something that could be > in the "description" file or noted in the contents of > publicinbox.$NAME.infourl. I wasn't sure what infourl was used for. :) Is it supposed to contain structured data, or is it more of a "click here for more info" kind of thing? > > listaddress = linux-kernel@vger.kernel.org > > listid = linux-kernel.vger.kernel.org > > archive-url = https://lore.kernel.org/linux-kernel > > archive-contact = postmaster@kernel.org > > I think the keys should match what we use in the config file, at > least. So s/listaddress/address/ and s/archive-url/url/ Okay. > I'm not sure if "contact" is necessary if the aforementioned > "infourl" exists. My thinking is that with mirrors of mirrors of mirrors, if someone submits a GDPR removal request, then there should be an easy way of figuring out where these requests should actually go. Maybe infourl can cover this, but it's less likely to be set up than an email address like postmaster@. So, I'm in favour of keeping that in the info record. > > Does that sound sane? > > I think so. Only the latest epoch would be taken into account, > I suppose. I'm actually thinking the other way around -- only the 0.git (or whatever is the lowest number), simply because it's more likely to have that record. That is, unless you want to add functionality to automatically copy these from previous epochs on auto-rotation events. -K