Date: Tue, 15 Dec 2020 15:58:58 -0800 From: John Baldwin <jhb@FreeBSD.org> To: git@FreeBSD.org Subject: Existing project/user branches in svn Message-ID: <97469514-737f-09a7-3ed7-50cf71846cec@FreeBSD.org>
next in thread | raw e-mail | index | archive | help
One thing I haven't seen mentioned is what is the plan for handling existing user/project branches from svn? And in particular, it doesn't seem it has been sufficiently communicated in that a new projects branch was added to svn this weekend with the conversion less than a week away. :( For branches that are actual branches of src, it seems like we should really be encouraging people to move that work into a git clone instead, and we probably need to let people now they need to be doing that this week since they won't be able to use svn for it going forward? (Will we be turning off commits to ^/user and ^/project when it converts?) This may require direct communications to people using svn this way (e.g. Rick Macklem still has an active NFS over TLS branch in ^/projects). For things in ^/user that aren't branches of src like freebsd-update bits, presumably those should be split out into separate repositories? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?97469514-737f-09a7-3ed7-50cf71846cec>