My apologies on the word-wrap (or lack-there-of). I didn't notice the
post was HTML until it was already well on its way.
- Valik
________________________________________
I posted this once before about a month ago but didn’t see any replies
in the archive. I’m posting again in the hopes that my first message
was unintentionally ignored rather than intentionally ignored because
nobody felt my comments were valid. Having been reading the list for
the past week or so and seeing how you guys quickly respond to things, I
think it was a case of the former more than the latter.
Anyway, the bulk of the original post follows.
I like the idea of storing previous commit messages, but I don't like
the location they are stored in. Doing a large number of commits or
committing with long messages will cause an unnecessary increase in the
size of the registry hive(s). Making the registry larger will in turn
begin to affect overall system performance since there will be more
stuff to process when applications access the registry.
My suggestion is to use a specially formatted file stored on disk to
hold the data. Storing on disk will not bloat the registry. Even
Microsoft states on MSDN that things should be stored on disk with just
a path stored in the registry instead of storing the contents of the
file directly in the registry.
The actual storage format or location doesn't matter. I can see INI or
XML files being used in conjunction with either a profile specific
location (%APPDATA%) or a public location with the correct file pointed
to by a string in HKEY_CURRENT_USER.
- Valik
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jul 7 20:18:03 2005