[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 4222]  Relative Externals cause repository corruption  when branch is renamed.
From:       cmpilato () tigris ! org
Date:       2012-08-23 15:27:07
Message-ID: 20120823152707.85F2454009B () sc157-tigr ! sjc ! collab ! net
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=4222



User cmpilato changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |INVALID
--------------------------------------------------------------------------------




------- Additional comments from cmpilato@tigris.org Thu Aug 23 08:27:06 -0700 2012 -------
Anne,

Per our issue tracker guidelines (at
http://subversion.apache.org/reporting-issues.html and
http://subversion.tigris.org/issue-tracker.html), your issue report should have
been posted to our users@ mailing list for discussion before being filed here. 
We require this process because we've found that it results in issue reports
which are easier to understand and reproduce.  For example, my attempts to read
your issue report leave me with many questions, mostly stemming from the lack of
detail (specific paths, specific client actions) and ambiguous terminology in
the report.

Per our policy, I'm closing this issue as INVALID, but don't think of this as a
value judgment on the problem you are seeing.  Rather, I'd encourage you to work
to construct a reproduction recipe script that uses the Subversion command-line
tools and begins with this step:

    svnadmin create issue-4222-repo

If you can post a script (to the users@ list) which begins like that, with an
empty data set, then populates some initial data and revisions, sets up the
externals definitions, and demonstrates the problems you are seeing when you
rename a branch, then we have some hope of understanding your report and solving
the problem.

And if you can't provide such a script, that's the point of the users@
interaction -- someone there can probably help you develop a reproducible recipe.

Thanks for understanding.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=3000505

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@subversion.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]