[Libre-soc-dev] git hashes are different?

[Jacob Lifshay]

On August 21, 2024 2:29:41 PM PDT, Dmitry Selyutin <ghostmansd at gmail.com> wrote:
> On Wed, Aug 21, 2024 at 9:41 PM Jacob Lifshay <programmerjake at gmail.com> wrote:
> > isn't that because you were still working on the code
> 
> That's not something local, the links from the tasks no longer point anywhere.
> The branch's still there, but links (with commit hashes) which used to
> be OK no longer work.

yes, that's because you rebased the branch (which creates new independent commits) and pushed the rebased branch, overwriting the only reference that was keeping the old commits alive.

I created and pushed two new branches to reference some of the old commits, which luckily were still in my git repo, you should do this yourself for any other broken links you find. The command I used to find chains of unreferenced commits, so i could push the deepest commits in those chains (turned out to just be the linked commits for those two cases):
git fsck --unreachable --dangling --no-reflogs | grep commit | sed 's/^.* \([a-f0-9]*\)$/\1/p; d' | xargs git log --graph

If you find any broken commits that you can't find in your repo, please post a message, maybe one of us has them still.

I pushed libopid-orig-for-bug-979-comment-51 and libopid-orig-for-bug-979-comment-59

> https://git.libre-soc.org/?p=openpower-isa.git;a=commitdiff;h=905dd24c769e74247935514f5ab8d462724ef798
> https://git.libre-soc.org/?p=openpower-isa.git;a=commitdiff;h=905dd24c769e74247935514f5ab8d462724ef798

those are the same link twice...oops

Jacob