merge with unversioned obstructions still broken in 1.6?
From: James Y Knight <foom_at_fuhm.net>
Date: Thu, 12 Feb 2009 17:38:56 -0500
I was really looking foward to 1.6's tree conflict feature. In
The documentation in http://svn.collab.net/repos/svn/trunk/notes/tree-conflicts/
I'll note that this would be a lot less irritating if issue #3101 was
Are either of these in the plans for 1.6 final?
James
Reproduction recipe below, if you're interested:
# Set up working copy (assume $repo points to a brand-new repository)
svn co $repo/branch
# Checkout trunk...
# Now on to the interesting part:
# # Merge branch back into trunk
# Oops, revert.
# But of course, revert leaves behind an unversioned "foo" file, even
# Now it lets me commit without raising a fuss, as if the merge had
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.