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

List:       subversion-issues
Subject:    [Issue 4330]  Merging from deleted branch requires version twice
From:       stsp () tigris ! org
Date:       2013-02-28 23:49:18
Message-ID: 20130228234918.94DE254005A () sc157-tigr ! sjc ! collab ! net
[Download RAW message or body]

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



User stsp changed the following:

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




------- Additional comments from stsp@tigris.org Thu Feb 28 15:49:18 -0800 2013 -------
Hi Christopher,

generally, you need to specify peg revisions when referring to deleted items in
repository history. Please see here for a detailed explanation:
http://svnbook.red-bean.com/en/1.7/svn.advanced.pegrevs.html

It has been suggested before to create a nicer invocation syntax for this use
case, and perhaps make Subversion locate the desired revision automatically.
However, no good solution is known for the general case, where a given
repository path like "/branches/B" might be added and deleted repeatedly over
time. The current implementation is the best we can offer right now.

I'm closing this issue as INVALID since the behaviour you are seeing is working
as intended in the current implementation of Subversion.

In the future, please post bug reports to the mailing list first.
See http://subversion.apache.org/mailing-lists.html for details on how to reach 
that list (you don't need to subscribe, and it is fine to post anonymously, too).

If you'd like to discuss improvements to Subversion's implementation I would
also like to ask you to do so on the users@ or dev@ lists, rather than using the
issue tracker for this purpose.

We use this issue tracker only to track the status of specific known and
confirmed bugs, or new feature suggestions which have received attention from   
the community. But discussion of all this happens on the mailing lists because  
the issue tracker isn't really a convenient tool to use for this purpose.

For the same reason this issue tracker isn't a support forum for users.
Our default course of action is to resolve issues such as this one as INVALID to
keep them off the list of issues developers and contributors are looking at when
trying to find something they could work on in the project.

Thanks for your understanding and I hope to see you on the list!

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

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