From nobody Sun Sep 14 00:51:03 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4cPV3H5hPqz67mgw for ; Sun, 14 Sep 2025 00:51:23 +0000 (UTC) (envelope-from chris.torek@gmail.com) Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4cPV3H2Bvcz41bx for ; Sun, 14 Sep 2025 00:51:23 +0000 (UTC) (envelope-from chris.torek@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-x231.google.com with SMTP id 38308e7fff4ca-351c164936eso17917561fa.0 for ; Sat, 13 Sep 2025 17:51:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1757811075; x=1758415875; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YLKNflux81JoxB1DyhqijmD3yuQH2gSddfTgYzx3gDk=; b=S7NK15B1EIqOg6qF4/B8q81UJu8ZZ/inU1VqEiDqH/Xd6VrAu0h4uFKOW/ZqElCJhu 8DFWW+zWuEBt58UA3sGkSfFCSyy8laBwGj2Ukk8tB3t3tXNkOr621fjZUxRWV5A2xlIl ul1cG5np0PLaOQ1pT+4PyAlpTiPQn72FEnKhyZj96pgHYZQ0hKEGedv7ubdwsHLbmjZz aGeXbepK1raw1mY6aHBLTgRWe2zeIiuCI35Uq6tDwWmFg9Yp+DNqIhutsTHikvEeWU45 yJ9AAgA7S+8udATXyPLuq86sXu5L2X/9LRDJSWwzC1J1W3dMTNZC04GfiQXiJCcdqFfx ZN+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1757811075; x=1758415875; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YLKNflux81JoxB1DyhqijmD3yuQH2gSddfTgYzx3gDk=; b=wjG2kYIUazNyLiKtU+7OrjF05hYCyG82KWPRSfrT2EPyZNt+LXpin1TV122rsh+5C6 c556vwrXy6t5wpnrQtVP0eYRX8Ux8sygFJiglhbgDD8LxwQAqA2ul1g0OmYTjVhmNnxM 3PxPraoBQSq4cdGlo3m6zXMUFqq2OiaSYR7DEbtVc2tEJ+EN71Ae1Qy6qbE/8PLQq1NT S5xIhY2KYdLaIJqzgLeCiq+6z/5wd8eDuooV7h4ln8MKbXBtSc9ZyvIoazqEp3aQRIld P4DJBjfv9jiROyOKLHkiBmkgGSe/noTmI5AJ4y1Uje27HvzWsG9kxM/axfsyQ7SpQzFO 7cIw== X-Gm-Message-State: AOJu0YwWuicFS0HFCGOoXDkN96HG7EPQ+UBPTsK4TGwROqkG3TUqU7ZZ v3klmNEC4r6eaCS6fAMTlgJ6FMokyIEhACoKI4sBxnpwG+HIpYnNMV06DD0yXFVpy/Cjo/JwsNS rsWZyufyOtCXxt+zBr9jGo312bMRv+hPzlBM7 X-Gm-Gg: ASbGnctdgonesJc4F3JogYX5BFxAy1yAndQKmCoo9vUm/R8rSc5SMzwLPMU1aM8rwtt f21pYBm4aAWw9w1UDdJnRzNIFTIyM8dUmIc9ePubaN3tZqLsvWkDDD2uAsRRNPjvzhIfP5wJMPl x/DHIbhyM0BswqGowiTct/G76wd4s0hnlQsuMqYJnjoM9uv2+sl25TORbNDHSHaIAWTY/qDatg0 rIUj2lq X-Google-Smtp-Source: AGHT+IHTfqW8iHGopQRicADAZVIfaSQsWb5rm3J09xarWgsw04/updMs9FHH9dxtoleR0zNHwr0Gikx0nKNgHtKUwWQ= X-Received: by 2002:a05:651c:4418:20b0:336:d1c3:37a7 with SMTP id 38308e7fff4ca-3513d579c3cmr19580341fa.26.1757811075162; Sat, 13 Sep 2025 17:51:15 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Chris Torek Date: Sat, 13 Sep 2025 17:51:03 -0700 X-Gm-Features: Ac12FXxs9POUFx7HB7mSPFR1o-xTdiN_GHbg72ZsYOBn91K1rlXXa13U7dqTus4 Message-ID: Subject: Re: Git and buildworld running at the same time To: bob prohaska Cc: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000b7a746063eb84861" X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4cPV3H2Bvcz41bx --000000000000b7a746063eb84861 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Sep 13, 2025 at 7:57=E2=80=AFAM bob prohaska w= rote: > 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. ... Git has its own housekeeping systems, including automatically re-packing repositories after a fetch (remember that `git pull` is nearly equivalent to `git fetch` followed by `git merge`). So this is likely normal Git behavior. Since the mid to late 2.40 versions of Git, "git maintenance" has more or less taken over as the "proper" driver for this kind of maintenance work, but since the Git folks do take compatibility quite seriously, "git gc" still does what it used to do and you can still use it (automatically or manually). Still, you might want to read the "git maintenance" manual page and set up a cron job to pre-fetch and pre-repack repositories. This should also make your merge operations [1] more convenient. Chris [1] "git pull" that is, though I personally avoid "git pull" and *always* run a separate fetch step anyway. This is partly for historical reasons dating back to Git 1.5, but I like to run a `git log` in between to look at the incoming commits. I use an alias, `git lin`, for "log incoming": [alias] lin =3D log ..@{u} Note that if you choose to use the new maintenance system, you must still run a separate `git fetch` anyway, so as to update the remote-tracking refs (`remote/origin/main` etc). It just tends to go far faster since you will already have the objects downloaded. --000000000000b7a746063eb84861 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Sep 13, 2025 at 7:57=E2=80=AFAM b= ob prohaska <fbsd@www.zefox.net> wrote:
Lately I've noticed that some= times 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. ...

Git has its own housekeeping systems, includin= g automatically
re-packing repositories after a fetch (remember t= hat `git pull` is
nearly equivalent to `git fetch` followed by `g= it merge`). So this is
likely normal Git behavior.

=
Since the mid to late 2.40 versions of Git, "git maintenanc= e" has
more or less taken over as the "proper" dri= ver for this kind of
maintenance work, but since the Git folks do= take compatibility
quite seriously, "git gc" still doe= s what it used to do and you can
still use it (automatically or m= anually). Still, you might want to read
the "git maintenance= " manual page and set up a cron job to
pre-fetch and pre-rep= ack repositories. This should also make
your merge operations [1]= more convenient.

Chris

[= 1] "git pull" that is, though I personally avoid "git pull&q= uot; and *always*
run a separate fetch step anyway. This is partl= y=C2=A0for historical reasons
dating back to Git 1.5, but I like = to run a `git log` in between to
look at the incoming commits. I = use an alias, `git lin`, for "log
incoming":
=
=C2=A0 =C2=A0 [alias]
=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0lin =3D log ..@{u}

Note that if you choose t= o use the new maintenance system,
you must still run a separate `= git fetch` anyway, so as to update
the remote-tracking refs (`rem= ote/origin/main` etc). It just tends
to go far faster since you w= ill already have the objects downloaded.
--000000000000b7a746063eb84861--