comment on

No I haven't searched the monastery explicitly, normally google is pretty good in digging them out. (probably I was only relying on DDG, though.)

This post looks interesting but as far as I was able to decipher between all the HTML errors, it's mainly describing the API of Alien::SVN and not how to enforce a commit.

Anyway I had an interesting chat with TomFahle on our local PerlMongers meeting and he had once a similar project. In his opinion Tortoise SVN is pretty messed up and my only chance be

identify all conflicting files with svn cleanup
moving the conflicts safely away
running svn up to get the old (conflict free) versions reestablished
moving the files back overwriting the old versions again while losing the conflict
now commiting

Haven't tested this approach yet, but it sounds promising. :)

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

In reply to Re^2: Daily bruteforced SVN commits by LanX
in thread Daily bruteforced SVN commits by LanX

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks