svn commit: r551373 - in head/dns: . knot3 knot3/files

[Alexey Dokuchaev]

On Tue, Oct 06, 2020 at 10:59:53AM +0200, Baptiste Daroussin wrote:
> On Mon, Oct 05, 2020 at 10:05:50AM +0200, Kurt Jaeger wrote:
> > Hi!
> > 
> > > > > 2) i vaguely remember that with the migration to git,
> > > > 
> > > > Ports cannot be migrated to Git for various reasons.  Even if they
> > > > could, we're currently using Subversion.
> > > 
> > > For the record, ports will be moving to Git within three to six months,
> > > either before 2021Q1 or if time is too short, 2021Q2.
> > 
> > Can the repo-copy procedure be seen in the git repo or is
> > the repo-copy lost after the migration ?
> 
> Repo copy is guessed after the migration

= pretty much fucked up: unreliable, CPU-intensive, and guessed wrongly for
anything but very simple cases*.  Either Git must be fixed and learn how to
track renames, or left where it belongs instead of trying to replace mature,
full-featured solutions such as Subversion.

Git is actually the worst in this regard, e.g. in Bazaar it allegedly works
even without requiring explicit move command**.

So, again: Git is rather poor choice for anything, but particularly bad for
the FreeBSD Ports Collection.

./danfe

*) https://stackoverflow.com/questions/29822823/how-does-git-know-that-file-was-renamed
**) https://how-bazaar.blogspot.com/2008/07/bazaar-has-model-right.html