Hello !
i missing an easy way to check a local checkout for conflicts.
Currently I'm grep the output of svn status for the existence of the
phrase „Summary of conflicts“.
This is ugly:
- needs LC_ALL=C ensurance
- may break in future versions of my the svn client.
A better way would to have an -
H.-Dirk Schmitt wrote on Tue, 09 Jan 2018 00:16 +0100:
> Hello !
>
> i missing an easy way to check a local checkout for conflicts.
>
> Currently I'm grep the output of svn status for the existence of the
> phrase „Summary of conflicts“.
> This is ugly:
> - needs LC_ALL=C ensurance
> - may break
On Tue, 09 Jan 2018 07:18:48 +, Daniel Shahaf
wrote:
>Bo Berglund wrote on Tue, 09 Jan 2018 07:49 +0100:
>> Is there some way to audit non-commit activity in Svn, specifically
>> checkouts?
>
>Yes, it's called "operational logging".
>See
>http://svnbook.red-bean.com/nightly/en/svn.serercon
Hi,
I am really confused by how to set an auto-property when I need multiple
"parameters" to a single property.
When setting svn:auto-props, it seems I can do this:
*.java = svn:mime-type=text/java;;charset=iso-8859-1;svn:eol-style=LF
That is, use ;; as an escape between the "parameters" for f
Chris wrote on Tue, 09 Jan 2018 15:15 +:
> When setting svn:auto-props, it seems I can do this:
>
> *.java = svn:mime-type=text/java;;charset=iso-8859-1;svn:eol-style=LF
>
> That is, use ;; as an escape between the "parameters" for file type and
> charset. Adding a java-file and doing propg
Hi Daniel,
thanks for the reply.
You're right that it seems to work when I do "svn add" and with that config
file, but when I do the same with svn_apply_autoprops.py, it acts badly. I
simply forgot to check the regular add :)
So I get the problem when I do:
./svn_apply_autoprops.py --config my
