Ralf Onat schrieb:
>> If you can give an example, you might convince more people than by
>> just stating the usefullness.
>
> Alright. It's pretty simple really. I update my working copy and
> notice that a file suddenly is 30MB instead of the "usual" 10MB.
> (This happens sometimes for .MDB files for various reasons).
>
> Then I do a show log and see that 10 commits have happened since my
> last update. OK so here's the use-case: which of these commits
> changed the file size so drastically?
>
> PS: of course there are also other reasons why files change in size
> and you would like to know why/where.
Thanks so far, but that was the obvious part.
You didn't quote the original question: You now know the file size
changed dramatically by 20MB in revision r1234. What do you do with that
information? Would you revert the change? Probably not, because it's
there for a reason. Hopefully someone put that reason in the commit
message and now you can read it.
But what's the use of it? You could read that message without knowing
the filesize.
Please don't get me wrong. What I'd really like to know is, if this
would be a helpful infomration for me as well. I'm also dealing with
binary files in some of my repositories, but never felt the need to know
the change in filesize.
Felix
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2633465
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-07-15 11:46:56 CEST