At Thu, 9 Oct 2025 10:32:53 -0400, Andrew Cagney <andrew.cagney%gmail.com@localhost> wrote: Subject: Re: irt: Re: Core statement on version control systems > > I'm now looking back through archives at GCC and FreeBSD and I'm > struggling to find such a document. Any one? For FreeBSD there's ample documentation of their process to switch, for both the first switch from CVS to SVN, plus from SVN+Perforce to Git. Here's Warner Losh's record of the Git conversion documents: https://github.com/bsdimp/freebsd-git-docs/ He also wrote a nice primer for users: http://bsdimp.blogspot.com/2020/10/freebsd-git-primer-for-users.html He also initially posted a blog entry about the first steps to Git here, and it's more or less a rationale document (it was also in the above docs collection but was elided at some point): http://bsdimp.blogspot.com/2020/09/freebsd-subversion-to-git-migration.html > > That list is missing at least two critical points where git falls > > short: > > - storing file rename data > > Is that a real requirement? Or a hangover from a better CVS wishlist? For what it's worth I just did a file rename in a project, and introduced a number of changes in the file during the rename, and Git (2.35) picked up on it all, rename and changes all clearly marked. 4 files changed, 85 insertions(+), 48 deletions(-) Makefile | 35 ++++++++++++++----- Makefile.end | 26 +++++++++----- Makefile.inc | 2 +- Makefile.internal => Makefile.main | 70 ++++++++++++++++++++++---------------- Maybe that's not what some people would call "storing rename data", but it works for me! -- Greg A. Woods <gwoods%acm.org@localhost> Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost> Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgpG2fM1_t8hY.pgp
Description: OpenPGP Digital Signature