On 2006, Aug 21, at 10:19, Byron Campen wrote:
> r6528 | (no author) | 2006-08-21 04:50:33 -0500 (Mon,
21 Aug 2006)
> | 1 line
> Changed paths:
> M /main/repro/BerkeleyDb.hxx
> M /main/repro/ResponseContext.cxx
I did not perform the commit, that came from elsewhere
(trimmed):
219.134.241.139 [21/Aug/2006:04:50:31 -0500] "PUT
[...]/
ResponseContext.cxx HTTP/1.1" 204 "SVN/1.3.1
(r19032) neon/0.25.5"
219.134.241.139 [21/Aug/2006:04:50:32 -0500] "PUT
[...]/
BerkeleyDb.hxx HTTP/1.1" 204 "SVN/1.3.1 (r19032)
neon/0.25.5"
> In addition, why is this commit not attributed to
anyone?
Allowing that to happen, though, was my fault. We missed
that in
production testing. Sorry about that. I have corrected the
ACL line
that was munged in migration from the old site and verified
that it
will not happen again.
Since that was definitely a bad and unauthenticated commit,
and it
was caught early so that only about 7 people had performed
updates
since that happened, I rolled the repository back to remove
it.
Matching IPs with previous usage, it appears there are 7
commiters
that updated after the bad commit (and before the commit was
removed), so they will need to take action (new checkouts,
etc) due
to the repository changing under them. I am re-sending this
message
to them separately to make sure they know.
My apologies for allowing that to happen,
Philip
_______________________________________________
repro-devel mailing list
repro-devel list.sipfoundry.org
https://list.sipfoundry.org/mailman/listinfo/repro-devel
|