I realize it's a workaround, not a solution, but doesn't
"svn merge -r BASE:HEAD --dry-run . ."
do approximately what you would want 'svn up --dry-run' to do?
Daniel
Rob Hubbard wrote on Fri, 17 Oct 2008 at 14:57 +0100:
>
>
> > I may be missing something obvious, but what would svn update
> > --dry-run provide which svn status -u would not? svn st -u
> > shows what's changed locally and what's changed in the
> > repository, so one could see where conflicts might arise upon
> ^^^^^
> > updating, no?
> >
>
>
> Well, as you said, and as I commented in
> <http://svn.haxx.se/users/archive-2006-10/0465.shtml>,
> $ svn st -u
> shows where conflicts *might* occur.
>
> On the other hand,
> $ svn up --dry-run
> would show where they *will* occur.
>
> Given that SVN already provides --dry-run for merge,
> I'm surprised that there is so much resistance to introducing this
> option for the update command.
>
> My impression is also that other users would find this option useful
> for other reasons.
>
> I'd *also* quite like to see the remote changes without my local
> changes,
> that is, show what files will be updated to my working copy
> irrespective of my local changes. That's a slightly separate issue.
>
>
> Thanks,
> Rob.
>
> _______________________________________________
> This email has been scanned for Softel by Star.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-17 16:05:17 CEST