From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: 02/02: gnu: next: Compress the executable. Date: Sun, 29 Sep 2019 15:43:45 +0200 Message-ID: <87a7an8bfy.fsf@ambrevar.xyz> References: <20190905095602.15524.75425@vcs0.savannah.gnu.org> <20190905095603.AC57A209A5@vcs0.savannah.gnu.org> <874l1qgc1j.fsf@elephly.net> <871rwuc3es.fsf@ambrevar.xyz> <87blvu32qm.fsf@gnu.org> <878sqxq4ga.fsf@ambrevar.xyz> <875zm0co0t.fsf@ambrevar.xyz> <87h85ipo14.fsf@gnu.org> <87muf9n8sc.fsf@ambrevar.xyz> <8736gw6xrh.fsf@gnu.org> <87y2yonng4.fsf@ambrevar.xyz> <87k19tg63u.fsf@ambrevar.xyz> <87v9tcm8ws.fsf@gnu.org> <87d0fjb5hi.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:60615) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iEZUM-0007N8-Gq for guix-devel@gnu.org; Sun, 29 Sep 2019 09:43:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iEZUL-0007b6-8S for guix-devel@gnu.org; Sun, 29 Sep 2019 09:43:50 -0400 In-Reply-To: <87d0fjb5hi.fsf@gmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Maxim Cournoyer , Ludovic =?utf-8?Q?Court?= =?utf-8?Q?=C3=A8s?= Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable True. I've been using Btrfs for my data for a little while and I'm very happy with it. I wonder how Btrfs fares for a Guix system. In many ways, Guix supersedes many of the features of Btrfs (snapshots and deduplication in particular). So I wonder if it's not redundant and possibly incurs a waste of energy. What's your experience, Maxim? =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl2QtREACgkQm9z0l6S7 zH/QZwf/cdztkFgiEVALpnf7jTZEyxtQ8wxtq1IREr4YHKFzgC5Tx/0kZHRxA+qB XifdwmW/YaiMzF7zXWy+C4mqHhnwlF+LRRIf8TJDaIfJt11djw7xqX7oeIxjxbet LMl0pGk4RMeECJUOfa3lVuCAw+npJxuNsjwpNpZN/FrJVKCTDL6jEFNkSkAfts5q wlVhiFJyH7C802w0ha5Z9/sf/3vuFwihxIWQO2xYkQggkQmpu/+3+HfAVQ74Eg7a ziFqmJUs2JOV7PyYt4EG2/4JZnDU7ArXObZPf1WqDtKwNGPelPg2XmT2myFhtA9n VbfXwf9iaaCTnaYyiIVlMWdJGPNkGw== =d4X+ -----END PGP SIGNATURE----- --=-=-=--