On Wed, 26 Mar 2014 19:41:38 +
Philip Martin wrote:
> Henrik Carlqvist writes:
> > Would people hosting public svn repositories think that it would be
> > nice if some people using my tool would make one svn connection for
> > each revision in the repository?
>
> It's a user problem as well
On Thu, 27 Mar 2014 11:25:33 +0100
"Bert Huijben" wrote:
> If you have any input on that thread, please let us know so we can just
> create the api you need to get the information you need.
My tool does not call use subversion api, it simply uses popen to call the
svn command line client.
So wh
> -Original Message-
> From: Henrik Carlqvist [mailto:hc...@poolhem.se]
> Sent: donderdag 27 maart 2014 07:47
> To: Mark Phippard; philip.mar...@wandisco.com;
> users@subversion.apache.org
> Subject: Re: svn2cvsgraph, how to best handle merges?
>
> On Wed, 26
On Wed, 26 Mar 2014 15:45:31 -0400
Mark Phippard wrote:
> We came to the same conclusion when we built the revision graph in
> Subclipse back in 1.5:
>
> http://subclipse.tigris.org/graph.html
On Wed, 26 Mar 2014 19:41:38 +
Philip Martin wrote:
That's a topic for the dev list and there was
We came to the same conclusion when we built the revision graph in
Subclipse back in 1.5:
http://subclipse.tigris.org/graph.html
Trying to do log on a whole branch with -g could even get quadratic loops
and take forever. Doing it one revision at a time was the only thing that
would work but then
Henrik Carlqvist writes:
> Would people hosting public svn repositories think that it would be nice
> if some people using my tool would make one svn connection for each
> revision in the repository?
It's a user problem as well since making a request per revision doesn't
scale well and will be v
