[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Inconsistent log reporting between two machines on the same repo,same file

From: Jody Shumaker <jody.shumaker_at_gmail.com>
Date: 2006-01-13 16:53:45 CET

On 1/13/06, Matt England <mengland@mengland.net> wrote:
>
> At 1/12/2006 07:14 PM, Jody Shumaker wrote:
> >Err it stops on a copy/rename? (rename = move). It certainly doesn't
> >"break" that scenario, it's doing exactly what it said it would
> do. Shows
> >the log entries back till the last copy/rename.
>
> I beg to differ: since when do I ever want to display the log for a
> file...and not show the entire log? (A little background: we are 'svn
> move'-ing the file *precisely* so that we can retain its history...instead
> of a just a simple copy-and-delete maneuver.)

An svn move is actually exactly that, it copies the file, then deletes the
old one. Subversion doesn't have direct rename support yet. As already
mentioned, the checkbox is there so you can view just the history since a
branch was created.

Yes, Zach and I now know to uncheck the cryptic 'stop-on-copy/rename' that
> it will show the entire log...but for those who are not TortoiseSVN
> experts, why do we need to know to check or uncheck this stuff?

Can you please explain to me how it takes an expert to realize that
'stop-on-copy/rename' means exactly what it says? It stops showing logs on
the first copy/rename it reaches. You obviously know what a copy/rename is,
and this checkbox says it stops on that. I really don't see how it takes a
TortoiseSVN expert to understand what the checkbox does. Can you possibly
suggest text for the checkbox that wouldn't appear cryptic to you?

In other words: what purpose does this checkbox serve? From what I can
> tell, it has a potential to cause much more harm then good.

I honestly can't remember what state it defaults to with a fresh install of
TortoiseSVN, but possibly it should be defaulted to off if it currently
isn't? I know I only turn it on for very specific cases where I only want to
know what happened on the branch.

But I'm willing to listen to an alternative perspective if someone can
> present a case better then "it does exactly what I think the checkbox is
> supposed to do."
>
> -Matt
>
>
Received on Fri Jan 13 17:32:19 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.