On 13.06.2016 01:24, Johan Corveleyn wrote:
> I have a (full depth infinity) working copy:
>
> parent
> \-- sub1
> \-- sub2
>
> I'd like to make it sparse, throwing out sub2, so it becomes:
>
> parent (empty)
> \-- sub1 (infinity)
>
> Is there a way to do that, without first m
I have a (full depth infinity) working copy:
parent
\-- sub1
\-- sub2
I'd like to make it sparse, throwing out sub2, so it becomes:
parent (empty)
\-- sub1 (infinity)
Is there a way to do that, without first making 'parent' entirely
empty (by executing 'svn up --set-depth
[ Please no top-posting on this list. Preferably put your reply inline
or at the bottom. I've reshuffled your replies a bit. More below. ]
>> On Fri, Jun 10, 2016 at 8:15 PM, Doug Robinson
>> wrote:
>>>
>>> The dichotomy is due to the expression of "knowing who is actually working
>>> on a file
On 12.06.2016 10:06, Yves Martin wrote:
> On Sun, 2016-06-12 at 02:11 +0200, Branko Čibej wrote:
>
>>> It's not a result of merge of individual folders. I find the pattern
>>> in the log for commits I've done and I have most definitely not gone
>>> out of my way to explicitly merge several subfolde
On Sun, 2016-06-12 at 02:11 +0200, Branko Čibej wrote:
> > It's not a result of merge of individual folders. I find the pattern
> > in the log for commits I've done and I have most definitely not gone
> > out of my way to explicitly merge several subfolders one-by-one.
>
> As I said, once the sub
