Yes the file in the wc is replaced.
But in the context menu there is already an option "Compare with wc". I
suppose that it compares with the same file from the previous revision.
It's just that it is not the default behaviour when double clicking (the
option text should be displayed in bold). In fact there is no default
action. So the behaviour is not coherent between commit and update screen.
But it may be intentionnal.
On 8/9/07, Andy Levy <andy.levy@gmail.com> wrote:
>
> On 8/9/07, Julien Nigay <killergege@gmail.com> wrote:
> > Hi !
> >
> > When I commit, I'm used to double click on a file which calls the
> "Compare
> > with base" option by default. So I can check the modifications I'm about
> to
> > commit.
> >
> > I'd like to know if there is a reason that this behaviour isn't
> implemented
> > on the "update" screen : if I double click on a file in the result list,
> > nothing happens.
> > Is it possible to set the "Compare with working copy" option by default
> ?
>
> By the time the file appears on the list in the Update screen, the WC
> has already been overwritten by the updated copy from the repository.
> So you'll be comparing a file with a copy of itself.
>
> Maybe what you want is Check for Modifications...Check Repository?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
Received on Thu Aug 9 15:23:18 2007