Date: Thu, 15 Oct 2015 20:36:03 +0200 From: Kurt Jaeger <pi@FreeBSD.org> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: Kurt Jaeger <pi@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r399250 - in head: . devel devel/mongo-cxx-driver devel/mongo-cxx-driver/files Message-ID: <20151015183603.GJ1019@fc.opsec.eu> In-Reply-To: <20151015173303.GC77492@FreeBSD.org> References: <201510141111.t9EBBfLS022109@repo.freebsd.org> <20151015120250.GB43539@FreeBSD.org> <20151015172213.GI1019@fc.opsec.eu> <20151015173303.GC77492@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > > > In this case, why it was not properly resurrected? > > Lazyness on my part, as there are 400+ other "New"er PRs in the queue. > > I just took one from the stale end of the queue to get that queue > > a tiny, tiny bit shorter. > Nonetheless, I'd kindly ask you (and everyone else reading) to do "svn cp" > when resurrecting previously removed port, as instructed by PHB and common > sense, thank you. On the one hand, you are right, we should all do it according to the books. On the other hand, if it makes it too tiresome with only very little gain, why doing it ? Even if the port was in the tree in the past and it is not resurrected, the repo still has the full history if one ever wants to know more about it. It might be a tad bit more inconvenient for someone to reconstruct it, but given that the port was missing for one year shows it's not high-prio for anyone. If it's really an important port, then I do agree that it should be done the proper and not the lazy way. -- pi@FreeBSD.org +49 171 3101372 5 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151015183603.GJ1019>