-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 hello Karl, replies below as usual :) ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, July 3rd, 2021 at 6:12 AM, Karl <gmkarl@gmail.com> wrote:
tag v0.9.0 commit 8f35a5c0 2020-10-07 tag v0.10.0 commit a6b2180 2020-10-12 branch v1.9.0 commit 3ac3396 2021-05-17 tag v1.9.0 commit ada7f97b 2021-05-17 tag v1.10.0 commit 764fa9dae6 2021-06-23 origin/releases ...
I found it. I have a local branch locally named v1.9.0 that contains commits on top of v1.10.0 .
I apparently merged something on top of my releases worktree and named it as an earlier version.
I try (some disappear) to take 24/7 terminal logs, so that may be reviewable if needed.
you can try increasing history size: in .bashrc, or .profile, or equiv, export HISTSIZE=500000 export HISTFILESIZE=10000000 note that if you use screen or tmux you'll want to compensate accordingly. regarding git confusion: i've also found visual git tools helpful tracking down merge and history issues. e.g. kdiff3, gitk or whatnot. in a tree view, you can see an odd merge or tag like you discuss above. best regards, -----BEGIN PGP SIGNATURE----- iNUEAREKAH0WIQRBwSuMMH1+IZiqV4FlqEfnwrk4DAUCYOYf1V8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0NDFD MTJCOEMzMDdEN0UyMTk4QUE1NzgxNjVBODQ3RTdDMkI5MzgwQwAKCRBlqEfnwrk4 DE+WAQCYfbn8zH0GXcOMy4vm07o2qVesOSL+RcYBuv767PCYFwD9G2JCeuQsboDz E/D2XkTzv3mg1l27+mkclPMp3lW8B3M= =fFzA -----END PGP SIGNATURE-----