From: Samuel Wales <samologist@gmail.com>
To: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
Cc: "Marcin Borkowski" <mbork@mbork.pl>,
"Peter Münster" <pm@a16n.net>,
help-gnu-emacs@gnu.org
Subject: Re: disappearing lines
Date: Mon, 16 Jan 2023 18:11:38 -0700 [thread overview]
Message-ID: <CAJcAo8vDYbwPd=pyfWvBCVDeQ1=b1F5CX=mhE7uttmuaH5goGg@mail.gmail.com> (raw)
In-Reply-To: <86y1q22ncd.fsf@duenenhof-wilhelm.de>
you probably already know this but backup-walker is a useful package
for a quick overview and i think there is a more generic one that
allows different backends [one could want git or rsnapshot but idk
which are supported].
in addition to git i use a shell script to compare old and new
versions. it is for if git is not working, i suspect git or magit
corruption [which i definitely do], and other purposes. as a sort of
double check.
i am currently wondering if it is possible to store a copy of files or
shas and times someplace and use them to detect silent [e.g. git-fsck
does not notice] corruption in files or in magit or git or even fs.
but i do not have a clear idea on this. i know there's a program
called bitrot that does one thing for this.
i wonder if you could automate narrowing to specific issues so that
you do not have to wade through large diffs?
is it possible you have hardware issues such as a flaky cable inside your kb?
i'd think other hw issues would be less likely given the specificity
of the format.
[still no guarantee i will notice any replies even if to or cc me :[
but i tryt o check occsionally. gmail filtering !@#$.]
next prev parent reply other threads:[~2023-01-17 1:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 13:19 disappearing lines Peter Münster
2023-01-16 14:42 ` Panagiotis Koutsourakis
2023-01-16 16:57 ` Arash Esbati
2023-01-16 19:31 ` Peter Münster
2023-01-16 19:46 ` Jean Louis
2023-01-17 6:50 ` Peter Münster
2023-01-17 15:00 ` Jean Louis
2023-01-16 20:24 ` Marcin Borkowski
2023-01-16 21:14 ` H. Dieter Wilhelm
2023-01-17 1:11 ` Samuel Wales [this message]
2023-01-17 6:56 ` Peter Münster
2023-01-17 19:47 ` H. Dieter Wilhelm
2023-01-17 8:20 ` Panagiotis Koutsourakis
2023-01-17 11:28 ` Peter Münster
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJcAo8vDYbwPd=pyfWvBCVDeQ1=b1F5CX=mhE7uttmuaH5goGg@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=dieter@duenenhof-wilhelm.de \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@mbork.pl \
--cc=pm@a16n.net \
/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).