...Reviving an old thread that relates to an issue I've been having...
I'd agree with Douglas here, there's a lot of scope for confusion after
using the Revision log "Update item to Revision" command. In my case I
really do want to use "Update item to Revision" rather than "Save
Revision to..." as I'm not just wanting to view the old revision, but
actually build it.
Is it feasible to introduce another explorer icon overlay to indicate
that a working copy reflects an old revision rather than the HEAD
revision, a warning in the "Check for Revisions" would be nice too.
(working with TortoiseSVN 1.3.3, Build 6219 - 32 Bit, Subversion 1.3.1)
Thanks
Richard Lang
Simon Large wrote
> Douglas Stonham wrote:
> >> Wrong! The overlay icons only tell you about changes _you_ have
made
> >> compared with the revision you got from the repo. To find out if
> >> HEAD in the repo is any different you have to update, or just check
> >> for modifications (click the 'check repository' button).
> >
> > OK, I guess this is my problem. I always think of a wc syncing with
> > the HEAD of trunk or a branch. I obviously just haven't used (T)SVN
> > long enough yet to have come across a circumstance where having a
> > file or files deliberately out of sync with HEAD is the intended
> > effect.
>
> Mixed revision working copies are difficult and I think SVN
acknowledges
> that it is not handled perfectly. There is a note in the manual to the
> effect that updating individual files to a different rev is not
> recommended just because it is so potentially confusing. That menu
item
> is only there because people specifically requested it, not because it
> is a good idea.
>
> A better way of looking at old revs is from the revision log
> dialog->save as... which allows you to save a copy (as an unversioned
> file) of an old rev for whatever reason you need it.
>
> >> Well that is exactly the same situation you get without doing
> >> anything funny with old revs. If someone else commits a broken
> >> change to the repo, you will not see it until you update your
> >> working copy.
> >
> > Yes, but in that case, you would have log messages on the server
> > telling you that changes had been made since your last commit.
>
> Provided that you know what rev your working copy is at. You can use
the
> svnversion commandline tool to pick that information up, and it will
> tell you that you have a mixed-rev WC. Hmm. Maybe we should add that
> functionality to TSVN.
>
> > My only point was that you no longer have a good indication that
your
> > files are 'in-sync' with the last copy of HEAD you updated to and
you
> > have no indication that this is the case.
>
> Understood. That is a problem with no easy solution, except to use
> update-to-rev sparingly.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed May 10 08:40:43 2006