Date: Mon, 10 May 2021 11:35:58 +0200 From: Mathieu Arnold <mat@freebsd.org> To: =?utf-8?Q?T=C4=B3l?= Coosemans <tijl@freebsd.org> Cc: Mathieu Arnold <mat@freebsd.org>, Muhammad Moinur Rahman <bofh@freebsd.org>, "ports@freebsd.org" <ports@freebsd.org> Subject: Re: Preferred way of repocopy in terms of git Message-ID: <20210510093558.jfjfgja6xvoeexqi@aching.in.mat.cc> In-Reply-To: <20210510112143.7cf635e0@FreeBSD.org> References: <953F2827-FE7C-4286-B6D5-867382A436C7@freebsd.org> <20210510073056.ixl6ypq3bgrp6nco@aching.in.mat.cc> <20210510112143.7cf635e0@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--u5iwizul256kdhz5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 10, 2021 at 11:21:43AM +0200, T=C4=B3l Coosemans wrote: > On Mon, 10 May 2021 09:30:56 +0200 Mathieu Arnold <mat@freebsd.org> > wrote: > > On Fri, May 07, 2021 at 11:32:48PM +0600, Muhammad Moinur Rahman wrote: > >> What is the preferred way of doing ports repocopy in git? In the hard > >> way I can see moving it into two locations and merging them. But is > >> there any easier way of doing it? > >=20 > > Well, here is what I did when I added lang/perl5.34: > >=20 > > cp -R lang/perl5-devel lang/perl5.34 > > # change stuff > > git add lang/perl5.34 > > git commit > >=20 > > I don't really see any other way to do this, Git has absolutely no clue > > about copies or moves. >=20 > It might still be useful to do the copy and changes as two separate > commits. Even if git doesn't do anything with that, our next vcs might > and reconstructing copy history is faster and less error prone with > unmodified copies. Well, the next VCS will probably be in more than ten years, and we have no idea what it would be. When that time comes, and unless we migrate to it from subversion up to the point where we switched to git, and migrate to it from git from there, all the previous copies/moves information is already lost. So, I don't think there is a point in making it harder on people. Making a note in the commit message, like, "I copied the files from xxx/yyy" is enough, maybe adding the commit hash if it is a resurrection. But Having two commits to "record" something that git cannot possibly know about is just not interesting, all it will do is add useless commits and blobs to the repository. --=20 Mathieu Arnold --u5iwizul256kdhz5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEEVhwchfRfuV0unqO5KesJApEdfgIFAmCY/npfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDU2 MUMxQzg1RjQ1RkI5NUQyRTlFQTNCOTI5RUIwOTAyOTExRDdFMDIACgkQKesJApEd fgIIeA//TZyf0697gZV/mAJwZnEa6kBoDMMsuPa8a+O8HQcCm0xAjamBXJNHZK1u gA5jRo6gbxPO1Dez0OA65WttYDmRtTacFYeuNCVsvV+JWYt1HfcUgxYDUdxJHpme M3aFGTVtqIFQd5FMJWyYIAMfwtTNa1CZFMIx0AJRNf3jZ9SAb7n6kONvIzoM120s i+ZEw28Q4gesfuopiaYz1x0063Xt9Vl8bh/W8YE7pEkm6zOiu31c4VZ0La44hWo9 JTcglB0U/N0NfxztJ7bzsW6H/LgB091RRqi7lhaix+fJbQm1zBz8+azf3xTgflQK qAxulerii0lIFG0z7rxGvT8FKGjxPxJ+R6Vkzww6DfTt+NbrSqrTPjC21tIW5gKy JoUZ19uA+6vb2u43qYvwhj3UJv5OgO4IgGHSXtW6eYKDqTKu+PG6OPXwSh8WaFk1 +uq+PBju7gBWwS9rssDNVG+XE2FJ4DWTKX5QO8SFTQ3BJRWDSceNZAgBtheIGVhj 000tZZ4GX4SKd2X9ECDfLt0IkkW4ZD3L+8v4UqJQ0y6RVmObPmgz5RjHaF9Uizc7 v15Cypb5nuMv199Cmz40K8Rk8goW6o1+ZdLsMNMfu0i9b36B9rwLJBS0ZSwybl/C 9arOOsOhKARHcJRRmCKJ2BsCuyq48szNYs+IgHJ7Xdai4GmBgOU= =eXYN -----END PGP SIGNATURE----- --u5iwizul256kdhz5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210510093558.jfjfgja6xvoeexqi>