Date: Tue, 5 Jan 2021 14:56:16 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: How to handle the pack files now we have switched to git? Message-ID: <751004982.112.1609854976464@localhost> In-Reply-To: <22d067ae-c204-0dc5-4195-2d1c07f35560@ingresso.co.uk> References: <22d067ae-c204-0dc5-4195-2d1c07f35560@ingresso.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Van: Pete French <petefrench@ingresso.co.uk> Datum: dinsdag, 5 januari 2021 12:08 Aan: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> 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 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 big pack file of objects, and the name of the opack file is the SHA1 of whatever is inside it. So if something chnages then the filename chnages - and thus rsync tries to move the entire lot all over again, even if the change is tiny. > > Does anyone have a solution to this ? Currently I am telling rsync to ignore .git when it sends the source, but am not entirely happy with that. > > But apart from that, git works fine ;) > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > Why are you not happy with ignoring .git? It sounds like a pretty reasonable thing to do for your setup. Otherwise (if you keep the .git dir) there is nothing you can do about this (AFAIK) and you will rsync quite some data now and then. Regards, Ronald. From owner-freebsd-stable@freebsd.org Tue Jan 5 15:58:23 2021 Return-Path: <owner-freebsd-stable@freebsd.org> Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EF6BE4C0839 for <freebsd-stable@mailman.nyi.freebsd.org>; Tue, 5 Jan 2021 15:58:23 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D9HGR3t98z4f2w for <freebsd-stable@freebsd.org>; Tue, 5 Jan 2021 15:58:23 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 105FwLV9014170 for <freebsd-stable@freebsd.org>; Tue, 5 Jan 2021 07:58:27 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) MIME-Version: 1.0 Date: Tue, 05 Jan 2021 07:58:21 -0800 From: Chris <bsd-lists@bsdforge.com> To: freebsd-stable@freebsd.org Subject: Re: How to handle the pack files now we have switched to git? In-Reply-To: <22d067ae-c204-0dc5-4195-2d1c07f35560@ingresso.co.uk> References: <22d067ae-c204-0dc5-4195-2d1c07f35560@ingresso.co.uk> User-Agent: UDNSMS/17.0 Message-ID: <29bff715b10eabac5559742d7df88a5b@bsdforge.com> X-Sender: bsd-lists@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4D9HGR3t98z4f2w X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>; List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 05 Jan 2021 15:58:24 -0000 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 seems to happen wuth git is that it has a big pack file of objects, > and > the name of the opack file is the SHA1 of whatever is inside it. So if > something > chnages then the filename chnages - and thus rsync tries to move the entire > lot > all over again, even if the change is tiny. > > Does anyone have a solution to this ? Currently I am telling rsync to ignore > .git > when it sends the source, but am not entirely happy with that. > > But apart from that, git works fine ;) Brilliant minds think alike. I use nearly the same routine. ;-) Have been doing so on svn(1) as well. FWIW the only difference between passing the archive with vs without the .git. Is that getting the details of what rev the source is at will not be available without the .git. Same on svn. For me this is only a minor inconvenience. To help overcome this in the past. I issued a 'svn info /usr/src >./SRC-REV'. Then simply passed that file along to the receiving host(s). OTOH it won't be (easily) possible to "up" the repo(s) from the receiving hosts w/o the .git. HTH --Chris > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?751004982.112.1609854976464>