You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Marc Strapetz <ma...@syntevo.com> on 2009/04/22 14:30:23 UTC
Unexpected svn add --depth behavior
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?)
--
Best regards,
Marc Strapetz
_____________
syntevo GmbH
www.syntevo.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1861225
Re: Unexpected svn add --depth behavior
Posted by "Hyrum K. Wright" <hy...@hyrumwright.org>.
On May 8, 2009, at 3:28 PM, Alan Draper wrote:
> I'm new here, so I don't know the process.
>
> What's the status of this? Think a fix will be coming soon? If not
> is it possible to revert back to a previous version of SVN? Or is
> there a workaround (besides deleting our entire working directory
> daily and re-checking out)?
>
> Maybe because we're in the early stages of site development, with
> lots of big changes, but this bug is killing us.
Are you referring to the bug fixed by this change:
http://svn.collab.net/viewvc/svn?view=revision&revision=37607 ?
If so, the fix is included in 1.6.2, due out Real Soon Now.
-Hyrum
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2129306
RE: Re: Unexpected svn add --depth behavior
Posted by Alan Draper <al...@draperhunt.com>.
I'm new here, so I don't know the process.
What's the status of this? Think a fix will be coming soon? If not is it possible to revert back to a previous version of SVN? Or is there a workaround (besides deleting our entire working directory daily and re-checking out)?
Maybe because we're in the early stages of site development, with lots of big changes, but this bug is killing us.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2121081
Re: Unexpected svn add --depth behavior
Posted by Paul Burba <pt...@gmail.com>.
On Wed, Apr 22, 2009 at 10:43 AM, Mark Phippard <ma...@gmail.com> wrote:
> On Wed, Apr 22, 2009 at 10:30 AM, Marc Strapetz
> <ma...@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
Re: Unexpected svn add --depth behavior
Posted by Mark Phippard <ma...@gmail.com>.
On Wed, Apr 22, 2009 at 10:30 AM, Marc Strapetz
<ma...@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. 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://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1861399