> Maybe you should try using tortoisesvn on windows? Other than that, I
> don't see why it is so hard to see the C status when you run an svn
> status from the command line. Also if you try to commit with conflicts,
> you will get an error.
It's not for me, it's for the people that work on the project. Yes, I agree, it doesn't seem too hard to miss it, but they do. I think the real issue is these are non-technical people. For most things, they do use TSVN, but I have a post process that needs to run after a update, so I have a batch file they execute.
I was just hoping there was a return code from SVN. I'll just bit-the-bullet and write a ugly batch file to deal with it.
Thanks, Ron
Phillip Susi wrote:
> Maybe you should try using tortoisesvn on windows? Other than that, I
> don't see why it is so hard to see the C status when you run an svn
> status from the command line. Also if you try to commit with conflicts,
> you will get an error.
>
> Ron wrote:
>> Is there a way to make the Windows version of svn complain louder if
>> there is a conflict?
>>
>> Just showing:
>>
>> C MyFile.txt
>>
>> can slip by too easy with a large number of files. Unless I am doing
>> something wrong, there is no ERROR return from svn that says there was
>> a conflict.
>>
>> I can't see to find any options for being more verbose on conflict.
>> Under UNIX, I would have a script that check for these, but a Window
>> batch file is just not that swift.
>>
>> Thanks, Ron
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 11 17:31:46 2005