Date: Mon, 22 Feb 2021 20:35:00 +0000 From: Rene Ladan <rene@freebsd.org> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: freebsd-git@freebsd.org Subject: Re: Ports Repocopy Message-ID: <20210222203500.GA75838@freefall.freebsd.org> In-Reply-To: <202102221945.11MJjCiO063445@slippy.cwsent.com> References: <202102221945.11MJjCiO063445@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 22, 2021 at 11:45:12AM -0800, Cy Schubert wrote: > When ports switches to GIT, given that there is no GIT equivalent to svn > copy will repocopy become a thing of the past? Will we live with this or > will there be some kind of procedure ports committers must follow to > approximate a repocopy? > There is indeed no "git cp", only "git mv", so unless I'm mistaken repocopies will be a past thing. It might be possible to (credits to portmgr): - create a branch, - copy/move the files and commit the copy/moves without any changes, - change the stuff, - commit, - merge into the main branch. Similar for resurrecting a port: - create a branch from before the port was removed, - change stuff, - commit, - merge into the main branch (using something like "git merge -s their" so that the resurrection branch overwrites the removal) But this would warrant a new script if it turns out to be feasible. I have not tried this yet. René
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210222203500.GA75838>