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

Re: Unexpected svn add --depth behavior

From: Paul Burba <ptburba_at_gmail.com>
Date: Wed, 22 Apr 2009 11:02:00 -0400

On Wed, Apr 22, 2009 at 10:43 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Wed, Apr 22, 2009 at 10:30 AM, Marc Strapetz
> <marc.strapetz_at_syntevo.com> wrote:
>> With SVN 1.6.1, when adding an unversioned directory (containing some
>> unversioned files) with --depth=empty, this depth will also be set to
>> .svn/entries file. Hence, resulting working copy is sparse and will
>> remain sparse also after adding contained unversioned files and
>> committing all added entries.
>>
>> If the user isn't aware of this fact, resulting update behavior (new
>> entries are not fetched), merge behavior, etc. can be quite strange. I
>> would suggest to set depth "infinity" to added entries regardless of
>> used --depth parameter (or am I missing something important here?)
>
> I have also found this.  I thought there was a thread about it, but I
> cannot find it.

Mike Pilato proposed doing what Marc suggests here:

http://svn.haxx.se/dev/archive-2009-04/0323.shtml

There were no objections, but not cries of enthusiastic support
either. Deafening silence really.

Paul

> Might have been a private discussion.  I agree it is
> a bug.
>
> This bites us in Subclipse because we do all adds as svn add -N so
> that only the specific items you select in GUI are added.
>
> --
> Thanks
>
> Mark Phippard

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1861679
Received on 2009-04-22 17:02:15 CEST

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.