From: Eric Wong <email@example.com> To: Konstantin Ryabitsev <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Recording archiver origins in git Date: Mon, 28 Jun 2021 22:12:36 +0000 [thread overview] Message-ID: <20210628221236.GA25399@dcvr> (raw) In-Reply-To: <firstname.lastname@example.org> Konstantin Ryabitsev <email@example.com> wrote: > 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 Is "source" necessary? It seems like something that could be in the "description" file or noted in the contents of publicinbox.$NAME.infourl. > listaddress = firstname.lastname@example.org > listid = linux-kernel.vger.kernel.org > archive-url = https://lore.kernel.org/linux-kernel > archive-contact = email@example.com I think the keys should match what we use in the config file, at least. So s/listaddress/address/ and s/archive-url/url/ I'm not sure if "contact" is necessary if the aforementioned "infourl" exists. > 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? I think so. Only the latest epoch would be taken into account, I suppose.
next prev parent reply other threads:[~2021-06-28 22:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-28 21:26 Konstantin Ryabitsev 2021-06-28 22:12 ` Eric Wong [this message] 2021-06-29 12:56 ` Konstantin Ryabitsev 2021-06-29 19:59 ` Eric Wong 2021-06-29 20:10 ` Konstantin Ryabitsev
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 List information: https://public-inbox.org/README * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210628221236.GA25399@dcvr \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Recording archiver origins in git' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/public-inbox.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).