Git: timestamps

On 06/01/2021 02:32, Jamie Landeg-Jones wrote: > Re: git non-time-sequential logs Warner Losh wrote: Not having timestamps on files cloned or viewed in cgit.freebsd.org is a nightmare too. I just clicked through and saw several time stamps quite trivially. Could you be more specific in

Re: boot loader blank screen

On 2021-Jan-5, at 17:54, David Wolfskill wrote: > On Wed, Jan 06, 2021 at 12:46:08AM +0200, Toomas Soome wrote: >> ... >>> the 58661b3ba9eb should hopefully fix the loader text mode issue, it would >>> be cool if you can verify:) >>> >>> thanks, >>> toomas >> >> I think, I got it fixed

Re: kldxref: /boot/kernel/kernel: too many segments

El día martes, enero 05, 2021 a las 01:11:14p. m. +0100, Herbert J. Skuhra escribió: > On Tue, Jan 05, 2021 at 01:01:33PM +0100, Matthias Apitz wrote: > > > > Hello, > > > > On an amd64 system r314251 a world and kernel built fine from SVN r368166 > > the > > installation with > > > > # make

Re: git non-time-sequential logs

On 1/5/21 2:36 PM, John Baldwin wrote: On 1/4/21 8:52 AM, John Kennedy wrote: On Mon, Jan 04, 2021 at 08:22:56AM -0800, John Kennedy wrote: The git logs in /usr/src aren't time-sequential, so maybe I shouldn't trust those dates above (I pulled it ~Jan 3rd and let it compile overnight), but I'm

Re: boot loader blank screen

On 2021-Jan-5, at 14:46, Toomas Soome wrote: > On 5. Jan 2021, at 00:59, Toomas Soome wrote: >> >> >> >>> On 4. Jan 2021, at 18:30, Toomas Soome wrote: >>> >>> >>> On 4. Jan 2021, at 18:22, John Kennedy wrote: This is a little weird. Somewhere between

Re: boot loader blank screen

On Wed, Jan 06, 2021 at 12:46:08AM +0200, Toomas Soome wrote: > I think, I got it fixed (at least idwer did confirm for his system, thanks). > If you can test this patch: > http://148-52-235-80.sta.estpak.ee/0001-loader-rewrite-font-install.patch >

Re: boot loader blank screen

> On 5. Jan 2021, at 00:59, Toomas Soome wrote: > > > >> On 4. Jan 2021, at 18:30, Toomas Soome > > wrote: >> >> >> >>> On 4. Jan 2021, at 18:22, John Kennedy >> > wrote: >>> >>> This is a little weird. >>> >>> Somewhere between

Re: aarch64 based on main 58661b3ba9eb : panic for "ufs_dirbad: /: bad dir ino 66371814 at offset 106496: mangled entry"

On 2021-Jan-5, at 13:28, Mark Murray wrote: >> On 5 Jan 2021, at 20:15, Mark Millard wrote: >> >> The machine is a MACCHIATOBin Double Shot. > > Thanks for the warning :-) > > I'm using an MBin/DS as my firewall/gateway, and in its Copious Free Time™, > an ARM64 build-box. > > How recent

Re: git non-time-sequential logs

Warner Losh wrote: > > Not having timestamps on files cloned or viewed in cgit.freebsd.org is a > > nightmare too. > > > > I just clicked through and saw several time stamps quite trivially. Could > you be more specific in your complaint? > > Warner I wasn't really complaining - If the git

Re: boot loader blank screen

On Wed, Jan 06, 2021 at 12:46:08AM +0200, Toomas Soome wrote: > ... > > the 58661b3ba9eb should hopefully fix the loader text mode issue, it would > > be cool if you can verify:) > > > > thanks, > > toomas > > I think, I got it fixed (at least idwer did confirm for his system, thanks). > If

aarch64 based on main 58661b3ba9eb : panic for "ufs_dirbad: /: bad dir ino 66371814 at offset 106496: mangled entry"

Later I give notes about the context. The failure reported . . . # panic: ufs_dirbad: /: bad dir ino 66371814 at offset 106496: mangled entry cpuid = 0 time = 1609844528 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x30 pc = 0x0081c654 lr = 0x0011ccb4

Re: Unofficial PkgBase Repository

> p.s.: if it feels slow, blame virtio + vnet This made it fast for me (rc.conf): ifconfig_vtnet0="DHCP -tso -lro" signature.asc Description: PGP signature

Re: git non-time-sequential logs

On 1/4/21 8:52 AM, John Kennedy wrote: > On Mon, Jan 04, 2021 at 08:22:56AM -0800, John Kennedy wrote: >> The git logs in /usr/src aren't time-sequential, so maybe I shouldn't trust >> those dates above (I pulled it ~Jan 3rd and let it compile overnight), but >> I'm going to repull all the sources

Re: git non-time-sequential logs

On Tue, Jan 5, 2021 at 6:08 AM Jamie Landeg-Jones wrote: > Ryan Libby wrote: > > > On Mon, Jan 4, 2021 at 10:08 AM Warner Losh wrote: > > ... > > > As for date order, we could also add a commit hook that requires the > date > > > to be properly set, but that creates friction for developers. Is

Re: git non-time-sequential logs

On Mon, Jan 4, 2021 at 9:06 PM David G Lawrence wrote: > > Yes. Git has never been a true/pure VCS. However, it does offer enough > > VCS-like features to create a shared distributed versioned tree that's > > useful to the project. > > > > As for date order, we could also add a commit hook that

Re: git non-time-sequential logs

Ryan Libby wrote: > On Mon, Jan 4, 2021 at 10:08 AM Warner Losh wrote: > ... > > As for date order, we could also add a commit hook that requires the date > > to be properly set, but that creates friction for developers. Is that > > friction worth the benefits? I don't think so, but as you say

Re: kldxref: /boot/kernel/kernel: too many segments

On Tue, Jan 05, 2021 at 01:01:33PM +0100, Matthias Apitz wrote: > > Hello, > > On an amd64 system r314251 a world and kernel built fine from SVN r368166 the > installation with > > # make installkernel KERNCONF=GENERIC > > endet with the following messages > > install -T release -o root -g

kldxref: /boot/kernel/kernel: too many segments

Hello, On an amd64 system r314251 a world and kernel built fine from SVN r368166 the installation with # make installkernel KERNCONF=GENERIC endet with the following messages install -T release -o root -g wheel -m 555 zlib.ko /boot/kernel/ install -T dbg -o root -g wheel -m 555

Re: git non-time-sequential logs

>Why is it that the project can't continue to operate the SVN server in > addition to Git, gatewaying with -current as is being done with 12-stable? > As a developer, I definitely need monotonic revision numbers and reliable > dates when I'm trying to troubleshoot a regression. I understand

Re: git non-time-sequential logs

David G Lawrence writes: >Why is it that the project can't continue to operate the SVN server in > addition to Git, gatewaying with -current as is being done with 12-stable? David, With all due respect: That question has been asked and answered so many times now, that it's time to

Re: git non-time-sequential logs

> Yes. Git has never been a true/pure VCS. However, it does offer enough > VCS-like features to create a shared distributed versioned tree that's > useful to the project. > > As for date order, we could also add a commit hook that requires the date > to be properly set, but that creates friction