From: ebiederm@xmission.com (Eric W. Biederman)
To: <meta@public-inbox.org>
Cc: Eric Wong <e@80x24.org>
Subject: public-inbox-init -V2 for lkml
Date: Wed, 04 Jul 2018 04:25:37 -0500 [thread overview]
Message-ID: <871scj2vzi.fsf@xmission.com> (raw)
I was playing with using git to get my own local copy of lkml and
unless I did something wrong I have found a bug in publc-inbox-init.
Baring some cheats (aka cloning from git.kernel.org) I followed
the directions up on lore.kernel.org, and the archives did not display.
# git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
# git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
# git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
# git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
# git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
# git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
# git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
#
# public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml linux-kernel@vger.kernel.org linux-kernel@archiver.kernel.org
#
# public-inbox-index lkml
I was able to solve my issue by applying the following patch to
objects/info/alternatives.
--- all.git/objects/info/alternates-old 2018-07-04 04:18:17.734755092 -0500
+++ all.git/objects/info/alternates 2018-07-04 04:18:11.874754952 -0500
@@ -1 +1,7 @@
+../../git/0.git/objects
+../../git/1.git/objects
+../../git/2.git/objects
+../../git/3.git/objects
+../../git/4.git/objects
+../../git/5.git/objects
../../git/6.git/objects
AKA adding the older git directories to all.git.
Is that the correct fix? Am I write in thinking that public-inbox-init
is failing to do that? Or am I missing something?
Eric
next reply other threads:[~2018-07-04 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 9:25 Eric W. Biederman [this message]
2018-07-04 10:50 ` [PATCH] v2: fill alternates with old epochs on init from mirrors Eric Wong
2018-07-05 5:18 ` Eric W. Biederman
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=871scj2vzi.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).