On Tue, 3 Jun 2014 20:06:09 +
Curtis Stiebler cstieb...@navegate.com wrote:
we had a power flicker
Power flicker, physical hard disk crashes, fires, shit happens every now
and then...
We do not have a backup of the repository structure
I was once told that the 3 most important tasks for a
On Wed, 26 Mar 2014 19:41:38 +
Philip Martin philip.mar...@wandisco.com wrote:
Henrik Carlqvist h...@poolhem.se 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
On Wed, 26 Mar 2014 15:45:31 -0400
Mark Phippard markp...@gmail.com 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 philip.mar...@wandisco.com wrote:
On Thu, 27 Mar 2014 11:25:33 +0100
Bert Huijben b...@qqmail.nl 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
I have written a tool, svn2cvsgraph
( http://svn2cvsgraph.sourceforge.net/ )
to graphically display svn revision graphs.
Since version 1.6.17 of svn, svn log -g no longer shows any merges when
examining the repository root. After a discussion, here
On Fri, 14 Mar 2014 17:15:15 +
Havlovick, Ron rhavlov...@curtisswright.com wrote:
This is for a fpga and I want the svn revision number to be within the
FPGA. When the revision register is read, it agrees with the svn
revision number.
Not how to do it. Is it possible?
It seems to me as
On Wed, 26 Feb 2014 20:41:38 +0100
Henrik Carlqvist hc...@poolhem.se wrote:
Now I have finally been able to create a small case where merge
information is lost.
I didn't get much response here, do you think that I should file a bug
report into the subversion issue tracker?
regards Henrik
Since a few years (I think it was with release 1.6.17 of subversion) the
merge information shown from svn log -g has been changed. The new way to
show merge logs means some improvements like less redundant information
and better performance. Unfortunately, when using these newer versions of
svn to
We will get with our System Admin and see what is going there.
The command dmesg might also give a clue on Linux systems.
regards Henrik
On Wed, 25 Jul 2012 11:17:55 -0500
Justin Johnson jus...@justinjohnson.io wrote:
The command svn log -vg is not returning merge info when I execute
the command while sitting in a working copy of the root level of a
repository or when I pass in the URL to the root level of root level
on the
Thanks for your quick reply!
Log on ^/ shows all revisions; adding -g includes no more revisions.
Yep, that is the problem. IMHO the flag -g should also give output which
shows merge information, not only on deeper levels but also on the root
level of the repository. I can understand if most
Last week we rebooted the NAS server which hosts the disk where
(among other things) our svn repositories reside, in order
to enable quotas on that disk. Since that time, we have been
unable to work with these repositories. We see the following
error messages
-
12 matches
Mail list logo
