[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Hackathon project: Dumping viewspec

From: Stefan Fuhrmann <stefan2_at_apache.org>
Date: Fri, 24 Nov 2017 16:34:15 +0100

Very nice, well done, sir!

-- Stefan^2.

On 24.11.2017 14:42, Bert Huijben wrote:
> Hi,
>
> At the Aachen hackathon I promised to write some code to spit out the sparse
> definition of a working copy, or in other words some initial dumb viewspec
> output.
>
> Testing this on a test working copy with
> [[
> $ svn switch --list \SharpSvn\trunk
> ]]
> I can now see output like
> [[
> svn checkout https://ctf.open.collab.net/svn/repos/sharpsvn/trunk@4003
> /SharpSvn/trunk
> svn update -r 4004
> /SharpSvn/trunk/imports/patches/openssl/201603-capi-sha-openssl-1.0.2.patch
> svn switch ^/branches/1.800x/contrib_at_4004 /SharpSvn/trunk/contrib
> svn update -r 0 /SharpSvn/trunk/LICENSE.txt
> svn update -r 4004 /SharpSvn/trunk/src/SharpPlink --set-depth files
> svn update -r 4004 /SharpSvn/trunk/src/SharpSvn --set-depth files
> svn update --set-depth files /SharpSvn/trunk/src/SharpSvn/Commands
> svn update --set-depth exclude /SharpSvn/trunk/build.info
> ]]
>
> So this new command spits out the shell commands necessary to create a new
> working copy with exactly the same layout and revisions as the existing
> working copy.
>
> This could be the starting point for an improved format, or for creating
> scripts that transform this in something more useful, e.g. by filtering out
> unnecessary details.
>
>
> I put the current code in a patch file attached to this message to allow
> discussing this feature before putting it on trunk.
>
> Bert
>
>
Received on 2017-11-24 16:34:24 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.