From: Samuel Wales <firstname.lastname@example.org>
Subject: [ot] git corruption in personal repo --- leave it alone?
Date: Sat, 21 Jan 2023 21:49:15 -0700 [thread overview]
Message-ID: <CAJcAo8vfqa2keAikj+BHgyfERoJfj6Cf_FBL9yQa8+nLmRTiUw@mail.gmail.com> (raw)
investigating the insane diff [intermingled entries] thread i found
correpted commuits using git log. for example,
this entry's qwerqwerqwer
previous entry's qwerqwerqewr
in other words, a task inside text of another tasks and not even
adjusted subevels. as a user i would not create that most liekly.
most likely is intra-hunk operations in an old version of magit not
worth reporting. but never mind that.
i was just curious if you were me, would you just leae he corrupted
commits, or is there a compelling reason to use ineractive rebase edit
and fix the commits and then maybe teh later commits will be less
insane or maybe there will be slme kind of message that will tell me
more that might be useful. or not. idk.
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
reply other threads:[~2023-01-22 4:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).