Date: Mon, 30 Jan 2017 07:48:48 -0600 From: John Marino <freebsd.contact@marino.st> To: Torsten Zuehlsdorff <freebsd@toco-domains.de>, marino@freebsd.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Cc: Mathieu Arnold <mat@FreeBSD.org> Subject: Re: svn commit: r432561 - head/lang/php71 Message-ID: <ea269d85-7ac7-11e2-0e72-a3328fcde991@marino.st> In-Reply-To: <5725262c-4152-c711-e53b-a509742bcba1@marino.st> References: <201701271852.v0RIqOvW033749@repo.freebsd.org> <6aebcd6a-0439-f23a-be9d-e06f46d3511b@toco-domains.de> <ce44c753-2d68-0899-b07c-cfaa92de1158@marino.st> <4dd6d654-4525-c440-83b1-6a22215f6020@toco-domains.de> <5725262c-4152-c711-e53b-a509742bcba1@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/30/2017 07:28, John Marino wrote: > On 1/30/2017 05:15, Torsten Zuehlsdorff wrote: >> >> I did exactly this. 2 months ago there was no DTRACE in php70. So >> copying the working-copy of php71 over the repo-copy would have not >> included the DTRACE option. Therefore the repo-copy wouldn't have had >> helped. > > EXACTLY. > Your mistake is leaving this at two months ago. > I meant check differences the day of committing, not check differences 2 > months ago. If you had not assumed that zero changes happened to php70 > that would affect php71 in a two month period, then you would rechecked > the diff before you actually commit and seen them. I would have noticed > the changes because I always run "svn diff" before committing. > > >> >>> You misunderstood r432567. >>> That wasn't to correct my commit. >>> That was to add the second missing item, DTRACE for aarch. >>> >>>> I just noted in this 2 month how hard it is to find somebody for review >>>> and second how hard it is to get such a patch reviewed. First the >>>> review.freebsd.org didn't work for me because it contains a bug with >>>> umlaut for years. And second a repocopy could not be displayed. >>> >>> Yes, the diff would have been displayed. >>> That's the benefit of repocopy. >> >> Maybe i wasn't clear enough: the repo-copy could not displayed in >> review.freebsd.org. If you say: its possible. Okay, than its just the >> umlaut-bug preventing the display of my patch. > > I am not talking about review.freebsd.org. > I'm talking about svn. > > >> But - no, you are not right this time. Doing a repo-copy without >> changing the copy will cause a svn diff to just list the files. The diff >> didn't even contain the revision copied from. To bring a path like this >> into the review tool you need at least the --show-copies-as-adds param, >> which defeats the purpose of a repo-copy in review. > > I don't think anybody was talking about review. > If you do repocopy correctly, we all get a commit mail that shows the > differences between the new version and the version it was copied from. > In this case, we got what looked like complete files added which is how > mat know that svncopy wasn't used. > To clarify, I get that you're saying that a repocopy you performed 2 months ago would have been based on the state of php71 two month ago. I'm basically saying that after 2 months, I either would have rebased the original proposal on the current php71 or at least reviewed each addition to php71 in the last two months. At some point the proposal "expires" and I think 2 months is definitely beyond that point. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ea269d85-7ac7-11e2-0e72-a3328fcde991>