On 10/28/2016 16:12, Dan Atkinson wrote:
> Hi Johan,
>
> The repository is on a local drive and I have several other
> repositories on the same drive as well that were unaffected.
>
> I do some tasks (update/tag) on the repository via the command line. I
> just checked and the version of SVN used o
Hi Amad,
On 11/1/16 1:48 PM, CM Analyst wrote:
Eric,
Thank you for your response.
Actually, we do copy executables to a "release" directory in SVN.
However, for that to happen, the release content has to be defined in
advance, completed the formal test cycle.
You could have another folder wh
Eric,
Thank you for your response.
Actually, we do copy executables to a "release" directory in SVN.
However, for that to happen, the release content has to be defined in advance,
completed the formal test cycle.
For some stakeholders, that's too late. Our challenge is really about how to
dete
Hi Amad
On 11/1/16 10:26 AM, CM Analyst wrote:
Hello,
In our environment, there is a need to identify one or more set of
files with a custom attribute. I expect SVN properties is the way to go?
For a given set of .exes, I want to attach an attribute using the SVN
property called "RC: Release
Hello, In our environment, there is a need to identify one or more set of
files witha custom attribute. I expect SVN properties is the way to go? For a
given set of .exes, I want to attach anattribute using the SVN property called
"RC: Release Candidate". My questions: 1) Is this approach a re
On Tue, Nov 01, 2016 at 12:14:32AM -0700, Eric Johnson wrote:
> Using: svnadmin --version
> svnadmin, version 1.9.4 (r1740329)
>
> The first time I ran into this, I simply added the -M option. Since the
> default is reported just "16", I added "-M 384", and noticed a significant
> speed bump. Howe
On Tue, Nov 01, 2016 at 12:14:32AM -0700, Eric Johnson wrote:
> Since I have on the order of 230,000 additional commits to check, I'm
> looking at 39 days before my repository finishes verifying. That's not
> really acceptable.
>
> Any suggestions? Am I doing something wrong?
You could try to
run
Using: svnadmin --version
svnadmin, version 1.9.4 (r1740329)
The first time I ran into this, I simply added the -M option. Since the
default is reported just "16", I added "-M 384", and noticed a
significant speed bump. However, I've got a repository where even this
big jump didn't fix the per
