On Sun, 21 Jan 2018 22:23:21 -0600, Ryan Schmidt
wrote:
>
>On Jan 20, 2018, at 10:25, Bo Berglund wrote:
>
>> I have found that there is a problem in our SVN repository, which was
>> converted from CVS using cvs2svn 2.5.0.
>>
>> It concerns two exe files which are corrupted when I check out or
>
On Jan 20, 2018, at 10:25, Bo Berglund wrote:
> I have found that there is a problem in our SVN repository, which was
> converted from CVS using cvs2svn 2.5.0.
>
> It concerns two exe files which are corrupted when I check out or
> export them. The trunk files have been expanded by 905 bytes or
On Sat, 20 Jan 2018 13:19:26 -0500, Nico Kadel-Garcia
wrote:
>I suspect you can simplify the whole situation a great deal by moving
>at least this project to its own Subversion repository. You should be
>able to to at least test and debug ideas by doing a cvs2svn of just
>that project and trying
On Sat, 20 Jan 2018 13:19:26 -0500, Nico Kadel-Garcia wrote:
>I suspect you can simplify the whole situation a great deal by moving
>at least this project to its own Subversion repository. You should be
>able to to at least test and debug ideas by doing a cvs2svn of just
>that project and trying
On Jan 20, 2018, at 4:03 PM, Julius Smith wrote:
>
> I was cruising along great with my subversion repos on my NAS and my
> working copies on Mac OS X Sierra, but after upgrading to High Sierra
> I see this whenever I try to check something in:
>
>> svn ci -m 'update'
> svn: E45: Commit fail