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.3 required=3.0 tests=AWL,BAYES_00,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-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 326261F4C0 for ; Thu, 24 Oct 2019 19:53:09 +0000 (UTC) Received: by mail-qt1-x82e.google.com with SMTP id o3so428409qtj.8 for ; Thu, 24 Oct 2019 12:53:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition:user-agent; bh=HQkr9AgE4D44gSV07AOo/sdp3TU00dWlw/QwzAK0qSA=; b=dRL8FkXDlR8RbUPKWzFV9kBokFiZhLlfiBRgQVjUBDdiBR3JOeguScIs1eNI65ctsg cf80GEeGQqT3TXF49ZogwlvtRS58jsyhsDo0bhmns17xEaoJM3QzVaVYereo3CI+t4+W AS3ubw/IE5818XPr0LbZ2MuDq5HRZuvYxkRWA= 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:mail-followup-to :mime-version:content-disposition:user-agent; bh=HQkr9AgE4D44gSV07AOo/sdp3TU00dWlw/QwzAK0qSA=; b=ZVDs4lGD+hFeKfHujJ/1zJNB6OuT8BNRveh2v/8pLfAww2eYq/3cG0LRiyKJai3ZfS kFSWsMCE11s8CVPMQIB5IDJnXhBtKNTMJxKBzgdVBKE5pLKcZjfVVb7/5UrsME9OqPh0 2c6AWrEU8PF11D7WStWlTY/QTfYP5I+iqqX2IjKYU2a9YL6iV1HwwQK0PQPTzwlKKwGE +fNo4rHMy55xfKeUSmMMCTJqUe1dmBV4RHjXy7lfCD/ikWOxIzm95mb8fXWu+RBGLi5w Y+xSJ9zcoeacK7G1vT5rswgrOi7rRM/6KKTPHIppJwcnWzUrEnvZUU/+BB2FbYIRZMOu vJfQ== X-Gm-Message-State: APjAAAWuX+t2FV9KyKbsnly8Mqrrl7DV938leSJn4N4Q/Zu/9v5tRW6l qmTmx6FFv42qHnxmU8A6PpIRSKTsGfs= X-Google-Smtp-Source: APXvYqxjSGJelcd2Y85JE3wUedzy24djW3jpecVCSKAkw/4Wrq5wQoaQHAuoRU0fEpXm6IoWrSS+MA== X-Received: by 2002:a0c:8b57:: with SMTP id d23mr16793580qvc.159.1571946787099; Thu, 24 Oct 2019 12:53:07 -0700 (PDT) Received: from chatter.i7.local (192-0-228-88.cpe.teksavvy.com. [192.0.228.88]) by smtp.gmail.com with ESMTPSA id t65sm13278841qkh.23.2019.10.24.12.53.05 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 24 Oct 2019 12:53:05 -0700 (PDT) Date: Thu, 24 Oct 2019 15:53:04 -0400 From: Konstantin Ryabitsev To: meta@public-inbox.org Subject: RFC: monthly epochs for v2 Message-ID: <20191024195304.5b7zlx7e3vxfxmtg@chatter.i7.local> Mail-Followup-To: meta@public-inbox.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline User-Agent: NeoMutt/20180716 List-Id: Hi, all: With public-inbox now providing manifest files, it is easy to communicate to mirroring services when an epoch rolls over. What do you think if we make these roll-overs month-based instead of size-based. So, instead of: git/ 0.git 1.git 2.git it becomes git/ 201908.git 201909.git 201910.git Upsides: - if history needs to be rewritten due to GDPR edits, the impact is limited to just messages in that month's archive - if someone is only interested in a few months worth of archives, they don't have to clone the entire collection - similarly, someone using public-inbox to feed messages to their inbox (e.g. using the l2md tool [1]) doesn't need to waste gigabytes storing archives they aren't interested in - since the numbers are always auto-incrementing, this change can even be done to repos currently using number-based epoch rotation, e.g.: git/ 0.git 1.git 201910.git 201911.git - there shouldn't be severe directory listing penalties with this, as even 20 years worth of archives will only have 240 entries Thoughts? -K