[RFC] Issue #3603 Fix - Should we do more?
From: Paul Burba <ptburba_at_gmail.com>
Date: Wed, 14 Apr 2010 14:28:19 -0400
Over the early part of this year Mike Pilato and other Collabnet
One merge related item that came up was: '--reintegration should
I created issue #3603 to track this.
The good news is that simply removing the check for a sparse WC works
If the reintegrate target is missing a subtree that *is* affected by
My question is this: Is that sufficient?
I think it is. It's not as if reintegrate merges can't result in tree
In a perfect world maybe we'd give a error along the lines of 'hey,
But going this route adds more merge special casing and obviously has
[[[
* subversion/libsvn_client/merge.c
(ensure_wc_reflects_repository_subtree): Consider shallow WCs as ready
* subversion/tests/cmdline/merge_tests.py
(reintegrate_fail_on_shallow_wc): Rename to...
(reintegrate_on_shallow_wc): ...this. Reimplement the test to expect
(test_list): Reflect test rename.
]]]
Paul
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.