On Sun, Aug 25, 2013 at 03:44:05PM -0700, Travis Brown wrote:
> I took a brief look at the resolution code and found it to be a twisty
> maze of callbacks and workqueues. There didn't appear to be any existing
> infrastructure or obvious way to resolve the tree conflict on the
> directory and then
On Mon, Aug 26, 2013 at 1:41 AM, Stefan Sperling wrote:
> On Mon, Aug 26, 2013 at 12:30:02AM +0300, Sergiy Tkachuk wrote:
>> Hello,
>>
>> I am using TortoiseSVN 1.8.1, Build 24570 - 32 Bit , 2013/07/22
>> 18:28:29, Subversion 1.8.1, -release, apr 1.4.8, apr-util 1.5.2,
>> serf 1.3.0, OpenSSL 1.0.1
Unsubscribe
Regards
John Birdsell
Acting Branch Chief
Database Manangement and Applications
US Dept of Labor
Office of Inspector General
200 Constitution Ave, NW
Room S5020
Washington, DC 20210
Hello
Can you provide me with a link as to how to apply this patch? When I search
for applying a subversion patch all I get is stuff involving svn diff. I think
the patch may be safer than using --force with switch for which all the
ramifications I do not even know.
-Original Message---
On 26.08.2013 15:31, John Maher wrote:
> Hello
>
> Can you provide me with a link as to how to apply this patch? When I search
> for applying a subversion patch all I get is stuff involving svn diff. I
> think the patch may be safer than using --force with switch for which all the
> ramificati
On Mon, Aug 26, 2013 at 01:31:49PM +, John Maher claimed:
>Hello
>
>Can you provide me with a link as to how to apply this patch? When I search
>for applying a subversion patch all I get is stuff involving svn diff. I
>think the patch may be safer than using --force with switch for which al
Thanks Travis.
I thought this was a binary patch, not a source code patch. Now I realize that
since subversion gets compiled into a variety of executables a binary patch can
not be done. I do not wish to compile subversion. I have found that --force
works and I only need it if switching to a
On 8/23/2013 4:09 PM, Maureen Barger wrote:
Has anyone made a jump this large before? Any comments about my upgrade plan?
We jumped from 1.5 to 1.8 on our server-side repositories. Our clients
were using a mix of 1.6 and 1.7 (most of the "important to us"
improvements in SVN 1.6 and 1.7 were
