ssion.
Current behavior is very annoying when doing multiple merge-commit
operations, especially into large working copy. In such case, I *know*
that I have up-to-date WC after each commit, but I still have to waste
time updating.
Best wishes,
Andrey Paramonov
--
This message has been scanned
e run 'svn update' instead.
I believe --ignore-ancestry should be enough to disable mixed-revisions
check.
Best wishes,
Andrey Paramonov
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
On 03.07.2012 13:20, Stefan Sperling wrote:
On Tue, Jul 03, 2012 at 11:56:47AM +0400, Andrey Paramonov wrote:
On 03.07.2012 11:50, Johan Corveleyn wrote:
Try '--allow-mixed-revisions'
Hmmm, svn help merge says:
--allow-mixed-revisions : Allow merge into mixed-revision wo
://subversion.tigris.org/issues/show_bug.cgi?id=4034
Thank you.
Hope it's clear that the problem only manifests itself for the locally
modified files.
Best wishes,
Andrey Paramonov
4 matches
Mail list logo