From owner-freebsd-current@freebsd.org Wed Dec 23 22:06:04 2020 Return-Path: Delivered-To: freebsd-current@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 584934CC9B1; Wed, 23 Dec 2020 22:06:04 +0000 (UTC) (envelope-from ml+freebsd@vishwin.info) Received: from varun.vishwin.info (varun.vishwin.info [46.101.93.59]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "varun.vishwin.info", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D1S2g0WTFz4Y0N; Wed, 23 Dec 2020 22:06:02 +0000 (UTC) (envelope-from ml+freebsd@vishwin.info) Received: from varun.vishwin.info ( [fd35:9eae:7575::2]) by varun.vishwin.info (OpenSMTPD) with ESMTP id cb149d7d; Wed, 23 Dec 2020 17:05:52 -0500 (EST) Received: from [IPv6:2601:98a:601:5140:56ee:75ff:fe50:69b5] ( [2601:98a:601:5140:56ee:75ff:fe50:69b5]) by varun.vishwin.info (OpenSMTPD) with ESMTPSA id ba4cc09e (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Wed, 23 Dec 2020 17:05:52 -0500 (EST) To: freebsd-current@freebsd.org, freebsd-git@freebsd.org References: <20201125055425.01AA628417@elsa.codelab.cz> <10f7b800-b015-2a80-b741-4f7db03bf6eb@quip.cz> From: Charlie Li Organization: FreeBSD mailing lists Subject: Re: git tools for building in base? Message-ID: <59893166-d05a-89b5-798b-c89e3392756b@vishwin.info> Date: Wed, 23 Dec 2020 17:05:49 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ITqAKabA1ofaueFaEpBppTBTtDVneuNLZ" X-Rspamd-Queue-Id: 4D1S2g0WTFz4Y0N X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.10 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; HAS_ATTACHMENT(0.00)[]; TO_DN_NONE(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[vishwin.info:+]; DMARC_POLICY_ALLOW(-0.50)[vishwin.info,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[46.101.93.59:from]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; TAGGED_FROM(0.00)[freebsd]; ASN(0.00)[asn:14061, ipnet:46.101.80.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[vishwin.info:s=fuccboi12]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; SPAMHAUS_ZRD(0.00)[46.101.93.59:from:127.0.2.255]; MAILMAN_DEST(0.00)[freebsd-current,freebsd-git] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2020 22:06:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ITqAKabA1ofaueFaEpBppTBTtDVneuNLZ Content-Type: multipart/mixed; boundary="HkyMKpgcNgAmUmZuUFENAarhoTqE23PJz"; protected-headers="v1" From: Charlie Li To: freebsd-current@freebsd.org, freebsd-git@freebsd.org Cc: uqs@freebsd.org Message-ID: <59893166-d05a-89b5-798b-c89e3392756b@vishwin.info> Subject: Re: git tools for building in base? References: <20201125055425.01AA628417@elsa.codelab.cz> <10f7b800-b015-2a80-b741-4f7db03bf6eb@quip.cz> In-Reply-To: --HkyMKpgcNgAmUmZuUFENAarhoTqE23PJz Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable Ulrich Sp=C3=B6rlein wrote: > I don't fully recall, but I think that the hg conversion was slow and > the disk space needed was quite a bit more than git. >=20 One of Mercurial's biggest design principles is immutable history (with history rewriting disabled by default), so increased disk space compared to git is reasonable. > So in summary, I guess it can be summed up as: > - there was no svn-all-fast-export for hg back then > - even bitbucket switched from hg to git Bitbucket dropping Mercurial support was more a business decision, although more ancillary tooling for git existing and developer appetite certainly played factors there. > - history rewriting is easier in git, see e.g. this file for the stuff = =C2=A0 > that's required to make the cvs2svn things a bit nicer: =C2=A0 > https://github.com/freebsd/git_conv/blob/master/fix_bogus_tags.sh >=20 > Granted, now that the heavy lifting is done, one could probably do a > git2hg transition, as the history is now pretty sane and should be > compatible to the hg model. >=20 Mercurial's branches are more similar to subversion than git. The hg analogue to git's branches are bookmarks, for which even they are optional since hg has its heads concept. > But lack of anyone (to my knowledge?) providing a hg copy of FreeBSD al= l > these years tells me that there's simply no demand for it. >=20 I use hg-beta for ports. Also used it for src up until git-beta came online. Not sure what I will do once ports is converted to git, however. My mercurial use stems from two sources: committers' need to preserve copy/move history (though this will probably go away with git) and horrendous performance with the ports tree in git. Horrendous as in, for example, takes about five minutes just to run git-status(1) on a ports tree stored on a hard drive with UFS (-uno doesn't help) whilst locking up the entire system I/O for the duration. The I/O lockups have since subsided but as of six months ago the slow enumeration has persisted. For some reason, mercurial is far more efficient in this regard. --=20 Charlie Li =E2=80=A6nope, still don't have an exit line. (This email address is for mailing list use; replace local-part with vishwin for off-list communication if possible) --HkyMKpgcNgAmUmZuUFENAarhoTqE23PJz-- --ITqAKabA1ofaueFaEpBppTBTtDVneuNLZ Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEE/3/Cqr5a+41PbEb+jnB43vIDq2wFAl/jvz4FAwAAAAAACgkQjnB43vIDq2x8 QQ/9HpolrtYaQlLG095p3vX8YdukhQLFOF743/tzT2kFrA/SKUD8XGZ7Q7xGEYnbvUB7P0bnajU0 Nr8CX3Sq6udD3L5FXUxXt/h7MVbxmtp6xvjEffthzaS0zNNqDOblzZoAD7tPYMqAF+QgniMuutJv HAluWdiS8URryJ8EkZRmxcnJYQ385NmAzi+0T0XCJuVdXASjBWf/5Gg9hdLhSQY4jOFKfx0EFF9F UFG3Ap/nh4TL0uXe4+aopQ+i6UskpsMRsIbuJnjsC7CfH0s3MvIseX8epzBPxfQb4V9g/3qi4wSm xVveHzNeaHwFnRXmS73aqlKgGqlzg6Qtwu15Llh+PBCL7J6HxnP7t3WAVOKlcKKMrhP7jWsax5z9 w1PjWDPUw5Si6bK016yOmQyXXF1c2oDeKqBIIxtzwjYb5UUGKrQMl0VAy+Espx1qwo+GIkCHqDVs v+KHr+UsHSad2lZHZQa9+0VtCvy5wLfDjMmrTIvB35A38mf2e7SC7WrupYgHpL/qSgoZbYOjhCKx VJYVH/CKou4AwCXSGhRX1sp9RXuQ2dSwvExJHyg+rvNEBY/7bW/OK8xTAYEe66m9TlkMcrSEDwFv KLpcivzonqSS/u9ZhW4tY8DEL8GfmhGkPsriUzs9TeZoWNQFlTGILcQPSM/FIMNJ2JnEUr36+heh +xo= =TVbD -----END PGP SIGNATURE----- --ITqAKabA1ofaueFaEpBppTBTtDVneuNLZ--