Issue #31 question.

All,
 
Apologies for not sending this to you first, but I figured a comment was not the same as a new issue.
 
In regards to #31, I've found that --include-empty-directories does not carry over its effects to /tags and /branches that are created by cvs2svn.  This leads to hand-wringing and chicanery.  I've tried to puzzle out how the directories are handled in trunk vs. branch creation and made little headway so far; I'm hoping, then, that you will be able to figure it out in one way or another more quickly than I could.
 
Thank you in advance for your attention.
 
--Jerry
 
 
The comment is as follows:
 
In regards to the comment of Mr. Fitzpatrick:

'One thing we should test is to see if checking out a branch or tag will get the
empty directory (in CVS).'

I would like to report that this is _not_ the case with the currently 
implemented workaround in post-2.3.0 trunk.  We have a repository containing 
empty build directories which, if not present, cause the build to fail.  
Leaving aside that discussion, when we convert the repo using --include-empty-
directories, it properly inserts the directories in the trunk, but sheds the 
directories when it populates the branches and tags, like so:

Added     /branches/foo
Deleted   /branches/foo/src/bar/A/bin
Deleted   /branches/foo/src/bar/B/bin
Deleted   /branches/foo/src/bar/C/bin
...

My thought was that this could be caused by one of two things:

1) The decisions to create empty subdirs in _make_empty_subdirectories are not 
recorded when it is time to create tag and branch paths on those same paths.

2) There was a programmatic decision that it was not possible to determine the 
origination point of empty directories in branches and tags, and/or that since 
tag/branch checkouts imply -P it was not necessary.  (I hope not, because 
updates insert the empty directories.  Thanks, cvs.)

Could someone take a look at this and consider whether or not it is fixable?  
Thanks for your attention.
***NOTICE*** This e-mail and/or the attached documents may contain
technical data within the definition of the International Traffic
in Arms Regulations and/or Export Administration Regulations, and
are subject to the export control laws of the U.S. Government.
Transfer of this data by any means to a foreign person, whether in
the United States or abroad, without an export license or other
approval from the U.S. Department of State or Commerce, as
applicable, is prohibited. No portion of this e-mail or its
attachment(s) may be reproduced without written consent of Kratos
Defense & Security Solutions, Inc. Any views expressed in this
message are those of the individual sender, except where the
message states otherwise and the sender is authorized to state them
to be the views of any such entity. The information contained in
this message and or attachments is intended only for the person or
entity to which it is addressed and may contain confidential and/or
privileged material. If you are not the intended recipient or
believe that you may have received this document in error, please
notify the sender and delete this e-mail and any attachments
immediately.

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2691014

To unsubscribe from this discussion, e-mail: [[email protected]].