The state of PSPGL #72

before you start to overwrite history, which will break all existing clones, could you first provide a diff with the changes between the repos ? i personally don't think the value of the real history is so important it justifies modifying a repo that's in use by potentially hundreds of people.
if both repos share a common ancestor it could be made into a branch "real-history" for people interested into that sort of thing.

This is a really good point. I guess just adding a new branch is better than completely overwriting the history.

I think that keeping past mistakes is not a good idea.

So if you want to keep the previous shas to avoid affecting "hundreds of users" (I bet there is not more than 10 xD, and most probably they are part of the pspdev community), you can rename the current branch to "legacy" and then rewrite the history of the current master/main.
I think that having maser/main branch as the "default" one, with the desired state is the best to do.

fwiw, i did a similar thing with my gnuboy repo - the original svn history is lost for eternity, but the original author provided me with a set of release tarballs and snapshots he had stored on his disk, so i first created "history" branch, then made a second branch based on that that fixed all build errors for the respective history with modern compilers, so the history could be used for bisecting. https://github.com/rofl0r/gnuboy/branches . i didn't modify master so people having a clone would not run into errors on pull.

In this case, let's do this:

1. Create a new branch in pspdev/pspgl (for example dev) and keep master as it is
2. Overwrite the history of just this branch
3. Make it the default branch
4. Request to attach a fork
5. Delete pspdev/pspgl-1

This way we will restore the correct commit history, keep the stars and won't break anything for anyone.

Docs: PSPGL (35 times)
Readme: pspGL (1 time)

it seems you misunderstood what i meant with content. i mean that foo.c will be identical in current repo and rewritten retro. not talking about commits.
i also said that pspgl is such a tiny repo that it doesnt matter when those few users have to clone it again. please read my post again with that in mind. it basically agrees with you entirely.

Ah, you don't want the file structure to change because of the transition to the newer code. That makes sense. I would also vote in favor or rewriting the git history to be able to merge these efforts.

right. i think before making the new repo with the rewritten history the official pspgl repo a recursive diff should be made so we dont actually have a code regression due to a mistaken omission of commits or anything else. apart from that i basically only wanted to express that i'm fine with however this ends up being implemented and don't want to stand in the way of the most pragmatic solution.

The only reason to overwrite the contents of the old repo instead of creating a new fork is to keep the stars and maybe some other metadata.

I think it's nice to have pspdev/pspgl. Easy to find.