Hi Dcz,
One point of clarification. Each JD does ** not ** have their own branch.
Each ** change ** has a branch. If the change is large and more than one
developer is working on the change, they will all work in the same branch.
Thanks
Lakshman
-Original Message-
From: dcz [mailto:d...@
Sometimes when I do a --reintegrate merge, I get some unexpected output, along
with the normal updates:
--- Merging differences between repository URLs into trunk-path
U /trunk-path/file1
U trunk-path/file2
trunk-path/file3
trunk-path/fil4
...
That is, I see a bun
On Feb 21, 2010, at 06:26, Gregory Berkolaiko wrote:
> Let's say
> .svn/text-base/README.svn-base
> got corrupted. For this discussion it is irrelevant "how" it got to
> be corrupted.
Well, to the Subversion mindset, that's the only thing that's relevant, since
Subversion assumes nobody chang
I am afraid you misunderstood my problem, or maybe I misunderstand you solution.
Let's say
.svn/text-base/README.svn-base
got corrupted. For this discussion it is irrelevant "how" it got to
be corrupted. The problem is that now the working copy is in an
unusable state and svn revert should res
