From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>, meta@public-inbox.org
Subject: Re: Warnings from git fsck after lkml import
Date: Thu, 12 Jul 2018 14:31:51 -0400 [thread overview]
Message-ID: <20180712183151.GA9085@chatter> (raw)
In-Reply-To: <20180705231346.GA6524@dcvr>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Thu, Jul 05, 2018 at 11:13:46PM +0000, Eric Wong wrote:
>"Eric W. Biederman" <ebiederm@xmission.com> wrote:
>> It looks like public-inbox has some challenges when importing some
>> questionable emails. The import of lkml has resulted in several commits
>> with bad dates that git fsck complains about. I have previously
>> reported this to Konstantin Ryabitsev who maintains kernel.org but since
>> I have not seen any discussion of this I thought I should report it
>> directly here as well.
>
>Thanks for bringing this up publically.
>
>Yes, I early during v2 development I noticed old mails had some
>-1400 timezone values (but the furthest is -1200). I opted to
>attempt to preserve the wonky timezones since fast-import
>happily accepts -1400 and I didn't anticipate problems...
So, I can fix those in the archives, but this obviously requires
rebasing the whole repo, and I'm not sure what kind of impact that would
have. I'm assuming it's not sufficient to just fix the git repo, as all
commit IDs after the modified commit are going to be different -- so
additional changes to sqlite and xapian dbs would be required?
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-07-12 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 5:40 Warnings from git fsck after lkml import Eric W. Biederman
2018-07-05 23:13 ` Eric Wong
2018-07-06 0:36 ` Eric W. Biederman
2018-07-06 3:47 ` Eric W. Biederman
2018-07-06 21:32 ` [PATCH] MsgTime.pm: Use strptime to compute the time zone Eric W. Biederman
2018-07-06 22:22 ` Eric Wong
2018-07-07 18:18 ` Eric W. Biederman
2018-07-07 18:22 ` [PATCH] Import: Don't copy nulls from emails into git Eric W. Biederman
2018-07-08 0:07 ` Eric Wong
2018-07-08 1:52 ` Eric W. Biederman
2018-07-12 18:31 ` Konstantin Ryabitsev [this message]
2018-07-12 22:19 ` Warnings from git fsck after lkml import Eric W. Biederman
2018-07-12 22:29 ` Eric Wong
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=20180712183151.GA9085@chatter \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=ebiederm@xmission.com \
--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).