On Mon, 19 Feb 2024 15:08:22 -0700, Vitaliy Aksyonov -> Nicholas Boel wrote:
VA> Then most probably it has 'soft CR'. You may dump message hex codes with 'I'.
I assume I'm looking for 8D somewhere? If so, there are none in the entire message.
I did notice a question mark in the message body:
00B0 C4 C4 C4 C4 C4 BF 20 C4 C4 C4 C4 C4 C4 C4 C4 C4 ?
But that's about it as far as anomolies.
VA> If you just want to use specific commit, then use git checkout. If you want
VA> to do binary search for broken commit - use git bisect interactively.
VA> Here's a tutorial, how to use it:
I used checkout to get the specific commit you asked me to grab (372220588c6f17cd3f709dcb721a9144169d988c), and it is indeed exactly how the latest version is. So you were right.
VA> And that's is very strange. I'd not be surprised if it was broken when I
VA> made first change (which was reverted by last commit), but looks like it
VA> worked fine.
It did not. Whatever first change you made actually kind of helped me, I suppose. Hopefully this helps narrow things down better and we can figure out what's going on.
Regards,
Nick
... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
|