MSGID: 1:154/10 65d3ea40
REPLY: 1:104/117 65d37cf8
PID: Smapinntpd/Linux 2.0 b20240216
CHRS: UTF-8 4
TZUTC: -0600
TID: hpt/lnx 1.9 2024-02-05
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)
SEEN-BY: 15/0 18/200 90/1 103/705 105/81 106/201 120/616 123/10 124/5016
SEEN-BY: 128/260 129/305 135/225 153/757 7715 154/10 30 40 50 700
SEEN-BY: 203/0 218/700 220/90 221/0 6 226/18 30 227/114 229/110 112
SEEN-BY: 229/113 206 307 317 400 426 428 470 664 700 240/1120 5832
SEEN-BY: 266/512 280/464 5003 5555 282/1038 291/111 292/854 8125 301/1
SEEN-BY: 310/31 320/219 322/757 341/66 234 342/200 396/45 423/120
SEEN-BY: 460/16 58 256 1124 5858 467/888 633/280 712/848 770/1 2320/105
SEEN-BY: 3634/12 5020/400 1042 5054/30
PATH: 154/10 280/464 460/58 229/426