Re: Tip of the day: Cheatsheet for common cmdline client operations

2017-09-18 Thread Pavel Lyalyakin
Hello, On Fri, Sep 15, 2017 at 11:57 PM, Johan Corveleyn wrote: > On Thu, Sep 14, 2017 at 5:27 PM, Pavel Lyalyakin > wrote: > ... >> I've spent some time to materialize the Quick Start document that I >> think will be helpful for novice SVN users. At the moment, it provides >> the most basic gui

Re: Tip of the day: Cheatsheet for common cmdline client operations

2017-09-18 Thread Johan Corveleyn
On Mon, Sep 18, 2017 at 6:00 PM, Pavel Lyalyakin wrote: > Hello, > > On Fri, Sep 15, 2017 at 11:57 PM, Johan Corveleyn wrote: >> On Thu, Sep 14, 2017 at 5:27 PM, Pavel Lyalyakin >> wrote: >> ... >>> I've spent some time to materialize the Quick Start document that I >>> think will be helpful for

Re: Sparse checkouts suggestion

2017-09-18 Thread Johan Corveleyn
On Wed, Sep 13, 2017 at 12:45 PM, Paul Hammant wrote: >> >> >> http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/svn-viewspec.py >> > > Excellent! > > I see you posted a StackOverflow answer on that too, Mark - > https://stackoverflow.com/questions/7481860/create-folder-structure-

Re: Sparse checkouts suggestion

2017-09-18 Thread Paul Hammant
I like the `svn co svn://vcs/trunk --view foo`. Well maybe if in a following `svn up` it would *remember the current view*, it would be good. > I'm not sure about listing the "available views" in a default > property, but okay, it's a possibility. I think it would be nice to be > able to read it

Re: Sparse checkouts suggestion

2017-09-18 Thread Branko Čibej
On 19.09.2017 00:59, Paul Hammant wrote: > I like the `svn co svn://vcs/trunk --view foo`. Well maybe if in a > following `svn up` it would *remember the current view*, it would be good. I don't think there's any need to remember the "current view": a sparse working copy already maintains its top

Re: Sparse checkouts suggestion

2017-09-18 Thread Paul Hammant
> On 19.09.2017 00:59, Paul Hammant wrote: > > I like the `svn co svn://vcs/trunk --view foo`. Well maybe if in a > > following `svn up` it would *remember the current view*, it would be > good. > > > I don't think there's any need to remember the "current view": a sparse > working copy already mai