Thanks, Paul.
I've tweaked the description to be slightly more verbose (we have
several 'svn cleanup' issues) and fixed the component (most probably
this is a bug in the library --- where the work is done --- not in the
thin layer that the cmdline client is).
Paul Maier wrote on Sat, Oct 23, 2010
filed Issue 3739
http://subversion.tigris.org/issues/show_bug.cgi?id=3739
Paul.
> -Ursprüngliche Nachricht-
> Von: Stefan Sperling [mailto:s...@elego.de]
> Gesendet: Donnerstag, 21. Oktober 2010 22:13
> An: Paul Maier
> Cc: users@subversion.apache.org
> Betreff: Re: 1.6.13: svn cleanup
In trunk, we have support for generating git diffs (with 'svn diff
--git'), and I believe the plan is to eventually support applying such
diffs too (via 'svn patch'). If you'd like to help with the 'svn patch'
work, please drop by the dev@ list and say hi. :-)
If you'd like to add something to co
Couldn't you just mount the online storage using whatever protocol they
support then run the encryption on top? In linux this would be like
ecryptfs on top of nfs. Not terribly performant, but it would
accomplish what you want.
On Mon, 2010-10-18 at 05:58 -0500, Gary wrote:
> I want to create a
Hi,
I would like to contribute a script for contrib/client-side.
It takes 'git diff' generated diff (with file copying and renaming)
and applies to working copy of SVN.
Where do I submit it?
Regards,
Armands
Guten Tag Bob Archer,
am Donnerstag, 21. Oktober 2010 um 17:57 schrieben Sie:
> No.. where is it?
I didn't see it, too.
http://www.open.collab.net/downloads/subversion/svn1.5.html
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
On Friday 22 October 2010, mfass wrote:
> I have two subversion servers. One is an open source repository not
> controlled by me, and the other is a closed source repository which is
> controlled by me. Both the open source and the closed source build
> together to make one set of software. The
> Just looking for anyone who may have a better way to do it, as the amount of
> files that are changing, could become large, not huge, but big enough to
> cause me to want to do it in a more automated fashion.
you should be able to achieve this by using git-svn or svk to create a local
copy. Make
