Francis Irving wrote:
>>- Shortcuts are _files_, which when treated as shortcuts can't be
>>versioned anymore (and that's what some people really want to do).
>
> Yes, that's true. The solution is to treat them as files if they are
> in a directory under subversion control (i.e. with a .svn folder), and
> treat them as shortcuts (act on the target) when they are not.
Wouldn't that confuse users? I mean they wouldn't really know why a
shortcut sometimes 'works' and sometimes not (until they read the docs,
but most won't do that but complain on the list instead or file issues).
Also: the chance that such a shortcut is invalid is very high - and
since NT4 (and Win2k in some cases) just crash if you try to follow such
a link the whole shell process would go down with it, since TSVN is a
shell extension. Bad, very bad...
>>Settings dialog, look&feel tab. You can there define yourself which menu
>>entries should show up on the top menu or the submenu.
>
> Yes, but I'm suggesting the default should be different.
That configuration was added so that we don't have to change the
"default" every time some users complain and the discussion about what's
default and what not start over and over again.
Sorry, but we won't change the default anymore - we did that already
three times, until I got really bored and added the settings.
>>I guess the second option here is better. But should I add another
>>button as you suggested or add a checkbox with "stop on copy"?
>
> Yes, that sounds good.
What exactly? The second button or the checkbox?
> Ah, I'm confused here. I'm doing the log on just one file, which is
> unlikely to have 7Mb of history. Are you talking about cases of
> recursively logging the entire repository?
You're used to CVS where each file has its own log history. Subversion
is different: all files share the same history - the whole repository
has global revision numbers. So if you fetch the log on a folder (e.g.
the /trunk/ folder), then you'll get the log of every revision at least
one file/folder below that folder has changed. There's no recursion done
for that - the server just filters the log messages out for those
changes not below the folder you've selected.
In Subversion, it's common practice to show the log for the whole
project folder. Only that way you can see what changed in the project,
what's been going on. If you would just select one file, you would miss
a lot of changes which are important for you, but happened to other files.
Sure, if you show the log only for one file, the history won't be that
big. But that's a rare case.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Oct 26 20:49:58 2004