Date: Sat, 13 Sep 2025 09:28:13 -0600 From: "Brad Davis" <brd@FreeBSD.org> To: "bob prohaska" <fbsd@www.zefox.net>, "FreeBSD Current" <freebsd-current@freebsd.org> Subject: Re: Git and buildworld running at the same time Message-ID: <f9ae18ca-13d9-4fdc-8ee4-6b1870ad67ad@app.fastmail.com> In-Reply-To: <aMWGWbI-8TwnAPnP@www.zefox.net>
index | next in thread | previous in thread | raw e-mail
On Sat, Sep 13, 2025, at 8:57 AM, bob prohaska wrote: > Lately I've noticed that sometimes while running buildworld a top > window reports git running also. Up to now, I've surmised that > this is intentional, with git providing some housekeeping function. > > Yesterday a buildworld session was accompanied by a prolonged > interval of git running also, with a large memory footprint, > near 1GB. That seems rather excessive. > > At the same time, it dawned on me that my recent habit has been > to run git pull, immediately followed by buildworld. Might it be > prudent to wait (how long?) to let git finish any housekeeping > triggered by the pull command? It seems likely that any overlap > could readily lead to inconsistencies which might account for > some of the buildworld problems I've been encountering lately. This is part of the normal build process and how the output of uname -a includes bits like this: main-n280188-2024887abc7d-dirty or main-n280188-2024887abc7d To find out of the src tree is pristine or dirty the build process uses git to find out. Regards, Brad Davishome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f9ae18ca-13d9-4fdc-8ee4-6b1870ad67ad>