On 06/01/2021 15:47, Ulrich Spörlein wrote:
That's not entirely correct. The packfile will only be rewritten if
a) enough other stuff has accumulated
b) you force a repack.
You are fighting against git's GC mechanism a bit here, but you can
still make it work. On your source of truth host,
On Tue, 2021-01-05 at 11:08:48 +, Pete French wrote:
So, for me the switch to git went very smoothly. I havent moved to
etcupdate yet, but will probably do that soon. Hopwever I did hit one
issue. What I do is to build on a single machine, and then send that to
a number of places using
On 05/01/2021 15:58, Chris wrote:
Brilliant minds think alike. I use nearly the same routine. ;-)
Always good to know that I am not doing something completely idiotic ;)
OTOH it won't be (easily) possible to "up" the repo(s) from the
receiving hosts w/o the .git.
Yes, this is my issue
On 2021-01-05 03:08, Pete French wrote:
So, for me the switch to git went very smoothly. I havent moved to etcupdate
yet,
but will probably do that soon. Hopwever I did hit one issue. What I do is
to
build on a single machine, and then send that to a number of places using
rsync.
But what
Van: Pete French
Datum: dinsdag, 5 januari 2021 12:08
Aan: FreeBSD Stable Mailing List
Onderwerp: How to handle the pack files now we have switched to git?
So, for me the switch to git went very smoothly. I havent moved to etcupdate
yet, but will probably do that soon. Hopwever I did hit
So, for me the switch to git went very smoothly. I havent moved to
etcupdate yet, but will probably do that soon. Hopwever I did hit one
issue. What I do is to build on a single machine, and then send that to
a number of places using rsync.
But what seems to happen wuth git is that it has a
