Hi
We are developing a fairly large application that uses open source libraries.
We have one svn repo per application. Currently, the open source libraries are
all stored with the application. This is a bad idea because the working copy
and repo are now very large. Also, every branch gets a
Around about 08/02/11 09:03, Daniel Shahaf typed ...
Thanks. However, to clarify, I'm not specifically interested in the
give us N revisions form; I'm just interested in seeing a coherent
patch at the end, and wanted to ensure you haven't forgotten that in
depth of coding.
Good luck / and
De : David Darj [mailto:z...@alagazam.net]
Envoyé : lundi 7 février 2011 18:12
À : RIBEIRO Philippe (i-BP)
Cc : users@subversion.apache.org
Objet : Re: TR: Problem upgrading to Subversion 1.6.15 on
Apache 2.0.64 / or on Apache 2.2.17
On 2011-02-07 14:47, RIBEIRO Philippe (i-BP) wrote:
Good afternoon!
I have a task to stress test our SVN server, but unfortunately I'd know how
to emulate some definite number of users and how to monitor server load
during the work of these users.
Please, can you recommend me how can I stress test SVN server, to what
metrics should I pay attention
Hi,
Thanks for your replies.
Installing Subversion 1.6.15 with Apache 2.2.17 and SSPI has been successful.
(I go on using SSPI to authenticate against an AD domain).
The problem was that I hadn't got the correct version of mod_auth_sspi (which
works with Apache 2.2.x). I found it on the net.
We are developing a fairly large application that uses open source
libraries. We have one svn repo per application. Currently, the
open source libraries are all stored with the application. This is
a bad idea because the working copy and repo are now very large.
Also, every branch gets a copy
On Tue, Feb 8, 2011 at 07:53, Harald Karner harald.kar...@gmx.net wrote:
Hi!
when I do a svn status -u I get the following result:
$ svn status -u test.txt dir1/
M * 210 test.txt
Status against revision: 213
* 212 dir1
Status against revision: 213
but
Subversion client works in Disconnected mode unless you go to perform some
function(s) that really create session with server unless it ends. Whenever
you need to test subversion performance and server load ; keep the following
parameters in your mind:-
· CPU Usage and monitoring
·
Hi Bob
Personally, hard drive space is cheap. I would rather have all the
dependencies for each project in my working copy. Sure, store it once in the
repository and use externals in your projects.
Thanks very much for your comments. I prefer your approach and have seriously
considered using
On 08.02.2011 15:34, Andy Levy wrote:
On Tue, Feb 8, 2011 at 07:53, Harald Karnerharald.kar...@gmx.net wrote:
Hi!
when I do a svn status -u I get the following result:
$ svn status -u test.txt dir1/
M * 210 test.txt
Status against revision:213
* 212 dir1
I sent this email Saturday in hopes of getting some help from someone with more
knowledge and experience than I have. However, I never heard anything back from
anyone. Because I'm new to the list, can somebody confirm that my messages are,
indeed, getting to the list? And does anyone have any
I want to be able to prevent commits to a repository in some circumstances.
I've set up a local svn repository to test, but my commit hook doesn't get
called.
I'm using the file:// protocol. Should hooks work with that?
There's a transcript of how to reproduce the issue here:
Johan Corveleyn wrote:
[dd]
But that doesn't explain why the resulting repository is so large
(compared to the original CVS repository). Sure, there might be memory
usage problems in dump/load (it uses more memory than the resulting
repository uses diskspace), but I think there is more going
Yes, you are right. The fundamental problem was that a good reliable and
scalable backup solution was missing.
Incremental svn dump looks promising.
Ankush
From: David Chapman dcchap...@acm.org
To: ankush chadha ankushchadha2...@yahoo.com
Cc:
On Tue, Feb 08, 2011 at 11:32:47PM +0600, Victor Sudakov wrote:
After the 15000th commit, the size of the repository on disk is 5.5G
with the working directory size being 120M. Besides, after several
thousand commits to this directory SVN slows down considerably. This
must be some design flaw
On 2/8/2011 1:34 PM, Stefan Sperling wrote:
On Tue, Feb 08, 2011 at 11:32:47PM +0600, Victor Sudakov wrote:
After the 15000th commit, the size of the repository on disk is 5.5G
with the working directory size being 120M. Besides, after several
thousand commits to this directory SVN slows down
I have a repository that I have configured to use path based permissions
via svnserve (additional config info below). Any user that has
authenticated has full read/write access to the entire repository while
anonymous users have read only access to a single path in the repository,
all other paths
Les Mikesell wrote:
On Tue, Feb 08, 2011 at 11:32:47PM +0600, Victor Sudakov wrote:
After the 15000th commit, the size of the repository on disk is 5.5G
with the working directory size being 120M. Besides, after several
thousand commits to this directory SVN slows down considerably. This
Stefan Sperling wrote:
After the 15000th commit, the size of the repository on disk is 5.5G
with the working directory size being 120M. Besides, after several
thousand commits to this directory SVN slows down considerably. This
must be some design flaw (or peculiarity if you like) of SVN.
19 matches
Mail list logo
