Date: Thu, 1 Apr 2021 09:30:49 -0600 From: Warner Losh <imp@bsdimp.com> To: Lars Liedtke <liedtke@punkt.de> Cc: freebsd-git <freebsd-git@freebsd.org> Subject: Re: Ports Repocopies Message-ID: <CANCZdfrEDBjk-1VXDOxdH_KgTOUkXfgWoq9TvNt%2BJEALCrc6uw@mail.gmail.com> In-Reply-To: <09169422-5c59-74a9-82ad-5d6d5fd17d7a@punkt.de> References: <202103311842.12VIgiJ3006095@slippy.cwsent.com> <20210401075841.xot2c427twdbxo5a@aching.in.mat.cc> <09169422-5c59-74a9-82ad-5d6d5fd17d7a@punkt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 1, 2021 at 4:39 AM Lars Liedtke <liedtke@punkt.de> wrote: > > > If you are talking about doing a svn copy/move to record the ancestry of > > I believe this is not true. Maybe git does it differently than svn, I > don't know that; but git does record moves and copies, whilst copies are > like new files for and moves are deletion and addition, git as far as I > know. This this might not be explicit but implicit. > git absolutely does not record copies or moves. It guesses. Usually it guesses right, but sometimes it doesn't. Whatever process we use, we need to assume that will fail at some point. To overcome this, be explicit where things were copied from, and hashes when ports are resurrected in the commit message. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrEDBjk-1VXDOxdH_KgTOUkXfgWoq9TvNt%2BJEALCrc6uw>