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_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (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 1EBB01F8C6 for ; Mon, 28 Jun 2021 21:26:14 +0000 (UTC) Received: by mail-qv1-xf32.google.com with SMTP id 11so3327471qvh.3 for ; Mon, 28 Jun 2021 14:26:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mime-version:content-disposition; bh=Pjjo+fGIe4vjUiM6VQYshoTcxZ7UyeXUNxlavAOkPYA=; b=T1Slpofp+3RLclPCOxj6rHhPl0RvihaSOUrGEhKXsP7/2f+pDCg7dmCKxLflHarN2i CWjHM4WeWPqJ2J7G9GesRzciS2mO3DrTOnabTt2+LkW1HxK3Fff2w5xEI9HbpaCa1FdM 6rLhd04mO1CSPcI4SUtY3+Gs7PeWwSCXKJpY4= 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:subject:message-id:mime-version :content-disposition; bh=Pjjo+fGIe4vjUiM6VQYshoTcxZ7UyeXUNxlavAOkPYA=; b=BQOsZDXz1Lk14LGnpKFHSza6QDdlHxCQF9Kvt40BUN+HpcO2i090s4DOM4iXyOEVcE TBl+RKpEcygLWATK5T6lsSCO460WvlW5OJ4TX5Lj1Er/9o0FXw8HTy4K6OiMDBZeunRx dUEjwbCucVNQyCETEj3YIboixAKunqOWKn6mNet4mNGCSIDyg7McrIaajyZCaQDoQAYg IJuL2D5lxg7IbyXMjlVakz/7K/4WB80krUws4h0fXU2o5HBiWP5hpS7sZxpOlL+WxnFk Mlv9vzAXdlTW95SV1HrHM5O2wnvkhgAA6gFKv25D9JRj3D0gZeMeiY0a0IwaPfoHFFYi ib/A== X-Gm-Message-State: AOAM530kIwNGISKVTo1XuNv9B12hYhP2+9BWDco/HjwhyGoNMfjHjj+g qWfzNaIdJuqb2UChsI80ms+RuoevlhwRDw== X-Google-Smtp-Source: ABdhPJyvr7tfDTW5l+N66G21xr7V/mn3E2g08BUaMW3H4cdXVn9RkKTt2rFPBDVJQPXNvj+tbftyHg== X-Received: by 2002:a05:6214:21e7:: with SMTP id p7mr26968290qvj.27.1624915572212; Mon, 28 Jun 2021 14:26:12 -0700 (PDT) Received: from nitro.local ([89.36.78.230]) by smtp.gmail.com with ESMTPSA id 202sm9590868qki.83.2021.06.28.14.26.11 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Jun 2021 14:26:11 -0700 (PDT) Date: Mon, 28 Jun 2021 17:26:10 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: Recording archiver origins in git Message-ID: <20210628212610.zbexle2b2uvux2sd@nitro.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Hello: I'm working away on grokmirror+public-inbox replication, and I'm trying to come up with a good solution for passing the "archiver origins" info. In examples/grok-pull.post_update_hook.sh, we try to get this information out of a curl call to the clone origin, but this may not be reliable for a number of reasons: 1. we may be cloning from an intermediary location that only serves the git repositories and the manifest file (e.g. erol.kernel.org) 2. the call may retrieve information relevant to the intermediary, and not to the origins of the archive I'm thinking of including a special location in the git repo itself for passing some of the same info currently found in the config snippet, e.g. in refs/meta/origins. Imaginary code snippet: $ git show refs/meta/origins:i [metadata] source = smtp 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 This way, even if the archive gets mirrored around a bunch of times, it's still possible to track where it originated, and if the original archive info becomes obsolete, someone can update the information without it affecting the rest of the archive. Does that sound sane? -K