From: Eric Wong <e@80x24.org>
To: Yaron Scheffer <yscheffer@protonmail.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
meta@public-inbox.org
Subject: Re: public-inbox-ssoma fails with lkml archive
Date: Wed, 19 Dec 2018 09:59:24 +0000 [thread overview]
Message-ID: <20181219095924.pdlun5jqu5vzgkte@dcvr> (raw)
In-Reply-To: <wHXDiZ3OVDpcB6hag6fh8o-_z133CT7CGLnF4YCQh_y3oWF2uZjMNYZYg3phUrppAd6tJRKVuo10GpkXPUsyY4koHzq7kRFsWVpuTEHaRdg=@protonmail.com>
Yaron Scheffer <yscheffer@protonmail.com> wrote:
> On Tuesday, October 23, 2018 5:33 PM, Konstantin Ryabitsev wrote:
>
> > The LKML archive uses the v2 format that was written specifically
> > to handle huge archives. I don't believe ssoma works with v2-formatted
> > repositories, but I'll let Eric provide the detail here.
>
> Thanks for clarifying. I lost several hours trying to debug this,
> I wish ssoma would die with an error when it detects a V2 archive.
> Is there a version tag somewhere under .git which can be used for
> this?
I'm very sorry about wasting your time. I've made
https://public-inbox.org/meta/20181219095057.21862-2-e@80x24.org/
which should warn on v2.
Also I'm sorry about the delay in replying to this message; too
many hardware failures this year and other crap to deal with.
Zbfg bs gur oynzr tbrf gb znvevk naq Tbbtyr pbqrfrnepu(*)
since the Terabytes Written count on my drives were insane.
I should start sticking my personal mail into public-inbox :x
(*) yeah, still kinda trying to be nice and not speak ill of other
Free Software projects...
prev parent reply other threads:[~2018-12-19 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 7:21 public-inbox-ssoma fails with lkml archive Yaron Scheffer
2018-10-23 14:33 ` Konstantin Ryabitsev
2018-10-23 22:47 ` Yaron Scheffer
2018-12-19 9:59 ` Eric Wong [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 \
--in-reply-to=20181219095924.pdlun5jqu5vzgkte@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.org \
--cc=yscheffer@protonmail.com \
/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.
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).