Date: Tue, 18 May 2021 00:08:36 -0700 From: Mark Millard via freebsd-bugs <freebsd-bugs@freebsd.org> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: freebsd-bugs@freebsd.org Subject: Re: "Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4" [really: list interface replacement generates bad textual content] Message-ID: <2365D754-7D28-46C0-B169-9BD5B729DD76@yahoo.com> In-Reply-To: <212C2CA4-4280-448F-A639-1B7B3E6DE356@yahoo.com> References: <1120D222-A28B-447B-9121-726BC8F49A7F.ref@yahoo.com> <1120D222-A28B-447B-9121-726BC8F49A7F@yahoo.com> <20210514210922.ygmuc3oigzd4ogi3@aniel.nours.eu> <9788E8D6-199E-4F48-89DA-F784BCC0CADF@yahoo.com> <5deb443a-316f-46b8-ada2-7f66893b5ffa@FreeBSD.org> <8AFC5AD7-8F1F-4980-BB26-62038380946E@yahoo.com> <03DFF722-0473-4306-B1C4-123DBF15B955@yahoo.com> <D34C4B97-C636-445E-87DB-5AA26438D912@yahoo.com> <c2022060-26b0-49b2-b2c3-416124b17937@FreeBSD.org> <9B7D4B8B-DD04-4119-8B80-548466D4F063@yahoo.com> <64429369-4010-4c99-888b-3460d9d9141e@FreeBSD.org> <3AF15926-17A0-4577-A673-AC35BE64BA7B@yahoo.com> <212C2CA4-4280-448F-A639-1B7B3E6DE356@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-May-18, at 00:03, Mark Millard <marklmi at yahoo.com> wrote: >=20 > On 2021-May-17, at 23:55, Mark Millard <marklmi at yahoo.com> wrote: >=20 >> On 2021-May-17, at 23:37, Baptiste Daroussin <bapt at FreeBSD.org> = wrote: >>>=20 >>>=20 >>> 18 mai 2021 06:50:03 Mark Millard <marklmi@yahoo.com>: >>>=20 >>>> On 2021-May-15, at 22:22, Baptiste Daroussin <bapt@FreeBSD.org> = wrote: >>>>=20 >>>>=20 >>>>> 16 mai 2021 05:29:07 Mark Millard <marklmi@yahoo.com>: >>>>>=20 >>>>>> In exploring I've seen various web-page presentation of >>>>>> freebsd-bugs messages that seem to be messed up. An >>>>>> example is: >>>>>>=20 >>>>>> . . . >>>>>=20 >>>>> Nice catch, I will fix it >>>>>=20 >>>>=20 >>>> The extra text disappeared when I later looked at the >>>> pages via the URLs. >>>>=20 >>>> But I've run into another oddity. I did a google >>>> search for: >>>>=20 >>>> "Comparing the OverDrive 1000 (A57) vs. MACCHIATObin" >>>>=20 >>>> and then used the 1st link shown, the one from the text: >>>>=20 >>>> QUOTE >>>> https://lists.freebsd.org =E2=80=BA freebsd-arm =E2=80=BA = 2019-December >>>> Comparing the OverDrive 1000 (A57) vs. MACCHIATObin ... >>>> Dec 2, 2019 =E2=80=94 Comparing the OverDrive 1000 (A57) vs. = MACCHIATObin Double Shot (A72) for buildworld and via a CPU/cache/RAM = tradeoff-exploring ... >>>> END QUOTE >>>>=20 >>>> which has the link (it is for one of my old messages): >>>>=20 >>>> = https://www.google.com/url?sa=3Dt&rct=3Dj&q=3D&esrc=3Ds&source=3Dweb&cd=3D= &ved=3D2ahUKEwiPhp3OtdLwAhVH6Z4KHaXQC68QFjAAegQIAxAD&url=3Dhttps%3A%2F%2Fl= ists.freebsd.org%2Fpipermail%2Ffreebsd-arm%2F2019-December%2F020854.html&u= sg=3DAOvVaw2VHrNUGc-Vce4CjAmTufxq >>>>=20 >>>> Or, extracting/converting the relevant part of that text: >>>>=20 >>>> = https://lists.freebsd.org/pipermail/freebsd-arm/2019-December/020854.html >>>>=20 >>>> This now takes me to the wrong message on the list, one titled: >>>>=20 >>>> Re: 64 bit ARM systems with more than four cores Ed Maste >>>>=20 >>>> Turns out that the my old message now shows up as 2 later >>>> by number (020854 -> 020856): >>>>=20 >>>> = https://lists.freebsd.org/pipermail/freebsd-arm/2019-December/020856.html >>>>=20 >>>> gets to the message with the correct title. >>>>=20 >>>> It appears that the numbering has not been preserved >>>> in the conversion. This can make google search results >>>> that point into the (older) freebsd lists >>>> problematical. >>>>=20 >>>>=20 >>>> =3D=3D=3D >>>> Mark Millard >>>> marklmi at yahoo.com >>>> ( dsl-only.net went >>>> away in early 2018-Mar) >>>=20 >>> 99.9% of the tume the numbering is preserved, sometimes it is not = given the weirdness of the things that happened in the past. i will dig = into this specific case to see what I can do. But don t expect much = here. >>>=20 >>=20 >> FYI: >>=20 >> In my "binary search inspired" looking around everything >> I looked at that was old but more recent than 2014-Dec-23 >> had the offset of 2. Everything older than 2014-Dec-10 >> worked. Those dates are as close together as I got. >>=20 >> (Finding things that have useful google search matches in >> a time frame is messy so the results are limited. It >> would be nice to find a better way to looking up old >> references.) >>=20 >> Example: >>=20 >> "lsof on FreeBSD/arm" goggle search click through to page >>=20 >> vs.: >>=20 >> Tuesday, 23 December 2014 >> . . .=20 >> =E2=80=A2 Re: lsof on FreeBSD/arm Larry Rosenman=20 >> =E2=80=A2 [Differential] [Commented On] D1317: Build gperf as a = dependency before gcc for arm releases emaste (Ed Maste)=20 >> =E2=80=A2 [Differential] [Updated, 8 lines] D1317: Build gperf = as a dependency before gcc for arm releases emaste (Ed Maste)=20 >>=20 >> It gets on to the message for last line (still off by two for the >> number, like what I reported already): >>=20 >> By contrast: >>=20 >> "watchdogd not working anymore (since r273154+)" google search click = through >>=20 >> vs.: >>=20 >> Wednesday, 10 December 2014 >> . . . >> =E2=80=A2 Re: RPi - watchdogd not working anymore (since = r273154+) Andreas Schwarz=20 >>=20 >> worked. >=20 > A different possible oddity that I just noticed is that > the old system used UTC dates/times, such as: >=20 > Mark Millard marklmi at yahoo.com=20 > Sat May 1 19:50:18 UTC 2021 >=20 > (from freebsd-git). >=20 > But the new one uses various time zones (the > senders time zone?), such as: >=20 > From: Mark Millard via freebsd-arm <freebsd-arm_at_freebsd.org>=20 > Date: Sat, 15 May 2021 14:43:45 -0700 >=20 > (from freebsd-arm). >=20 Well . . . freebsd-arm's messages have a UTC time after the message, such as: Received on Sat May 15 2021 - 21:43:45 UTC so both time zones are available. It might be deliberate. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2365D754-7D28-46C0-B169-9BD5B729DD76>