From: Konstantin Ryabitsev <firstname.lastname@example.org> To: Eric Wong <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Recording archiver origins in git Date: Tue, 29 Jun 2021 16:10:47 -0400 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <20210629195957.GA12571@dcvr> On Tue, Jun 29, 2021 at 07:59:57PM +0000, Eric Wong wrote: > > 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. > > I'm a little worried about it having too many directions > (e.g. webmaster vs postmaster) and something freeform like > infourl can cover it. Or we maybe something with user-defined > labels would work: > > contact = postmaster firstname.lastname@example.org > contact = GPDR https://our-lawyers.example.com/form.cgi > contact = webmaster email@example.com Maybe more RFC2822-like: contact = postmaster <firstname.lastname@example.org> contact = GPDR <https://our-lawyers.example.com/form.cgi> contact = webmaster <email@example.com> Should be kosher with git-config and a bit more obvious that one is a label. > > 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. > > It should be easy to change this info down-the-line in case of > project name/hosting changes, forks, etc. So whatever's latest > should supercede the older. It would also allow partial mirrors > to work with only the latest epoch(s) (I expect a partial > mirrors of recent epochs to be more useful than mirrors with > only old epochs). OK, I'm not picky and it's easy to reverse the dir listing. I'll trial it out on some lore archives and then share the resulting hooks. -K
prev parent reply other threads:[~2021-06-29 20:10 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 2021-06-29 12:56 ` Konstantin Ryabitsev 2021-06-29 19:59 ` Eric Wong 2021-06-29 20:10 ` Konstantin Ryabitsev [this message]
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --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).