On 08.04.2015 20:00, Evan Driscoll wrote: > [I typoed some keys and apparently happened to hit send while still > typing; let's try again. Sorry for the spam.] > > On Fri, Apr 3, 2015 at 4:25 PM, Branko Čibej <br...@wandisco.com> wrote: >> Would this tell you what you need (given a checkout of 'trunk'): >> >> svn diff --summarize ^/trunk@<revision> . >> >> This will give you a summary of the differences between your current >> working copy state and the tree in the repository at <revision>. > Sorry for not responding right away, but I just had opportunity to try > this out. And it definitely helps; it's much closer to what I want > than anything else I know of, so thank you very much for bringing my > attention to it. > > However, it's still not great. First, it won't tell you if you'll get > any conflicts, so in that sense it's not the same as an `up --dry-run` > would be. Second, it seems to list as "M" files that have been locally > modified (in a way that disagrees with ^/trunk@revision), even if > those files won't be affected by the update. So for instance, `diff > --summarize` gave me 12 "M" files in the working copy I was just > using, but only 7 files were changed when I updated to that revision.
Indeed. This is caused by a limitation of our server-side APIs, > So I still posit that `up --dry-run` is not redundant and would be > useful. If you have a chance to test the latest Subversion trunk, 'svn status -u' now accepts a revision parameter too. With a bit of luck, the upcoming 1.9.0 release candidate will have this feature, too. -- Brane
