[spam][wrong] new git history for mailman
hey I did a "git pull" in my mailman git repository recently and it said it couldn't merge cause there was no common ancestor between the trees that's kinda frustrating, could things go better than that?? anyway I tarred the folder up for possible archival of both histories
On 4/17/22, Undiscussed Horrific Abuse, One Victim of Many <gmkarl@gmail.com> wrote:
hey I did a "git pull" in my mailman git repository recently and it said it couldn't merge cause there was no common ancestor between the trees
that's kinda frustrating, could things go better than that??
anyway I tarred the folder up for possible archival of both histories
Various project repos have emitted this message. As with any change in keys, projects should probably announce why for transparency, unfortunately that is rarely done. When people see the message, they should ask the project why. And do a diff between copies to see if anything interesting changed. Interesting changes have been seen before... in sensitive projects, most were defensive, rather than suspect. If the change is suspicious, people should publish their observation for review.
as a govcorp zombie, my knee jerk reaction in situations like this is to prevent analysis and spread fear or discredit, unfortunately. it's very hard to do otherwise. atm i'm in bed and would diff the trees and maybe contact the repos if near the system with the old content, but it's very hard: - it can take me hours to stand up out of bed and I have frequent amnesia during that time - my system has malicious compromise that can harm file content, and my brainwashed alter knows how to trigger the compromise live so I basically establish a norm of half-delusional paranoia, that can spread from my behaviors to others
participants (2)
-
grarpamp -
Undiscussed Horrific Abuse, One Victim of Many