On 20.09.2011 15:05, Marcus Denker wrote:
On Sep 20, 2011, at 2:54 PM, Henrik Sperre Johansen wrote:
On 20.09.2011 14:49, Marcus Denker wrote:
Hi,
The .changes have gotten really large... (32MB...)
So I will do a condense in the next update.
NOTE: this will take quite some time to finish, so maybe wait for a pre-built image or Jenkins...
Marcus
-- Marcus Denker -- http://marcusdenker.de
Noooooooooo, please please don't... Method history is so much more useful than 20 extra MB's on my HD :S
Ok, so lets postpone... but we really need to think hard how this is sustainable.
I have the impression that the current source management system needs some real improvement soon.
Marcus
-- Marcus Denker -- http://marcusdenker.de
Can only speak from personal experience... When encountering a bug in some recently changed method, your only chance is manually diff each package from around the changeset timestamp, and you'll hopefully be able to link it to the issue that prompted the change... Now imagine this when there are nothing but most recent versions in the .cs, and some syntactic changes were made after that which actually introduced the bug? Yup, (imho) condensing changes make linking method changes back to the issues which prompted them practically impossible. (and before that, it's still a PITA) Performant method history browsing from Monticello repositories is never going to be a reality. I'd gladly give 100 ⬠(or a beer, whichever is preferred) to someone who can prove me wrong :) Cheers, Henry