On Sun, Nov 21, 2010 at 9:54 AM, Kevin Connor Arpe wrote:
> Hello,
>
> I have a question about version caching. I am using the latest
> (stable) version on both Linux and WinSlows.
>
> As I understand Subversion, once a version is committed, basically it
> can never c
even
if they aren't referred to by any current file).
None of the above addresses log messages; however, for that you could
use other solutions. One way is to enable commits mails and never
delete them.
Andrey Repin wrote on Sun, Nov 21, 2010 at 18:36:20 +0300:
> Greetings, Kevin Connor A
Andy Levy wrote on Sun, Nov 21, 2010 at 11:14:43 -0500:
> Subversion only caches logs on the client.
Subversion itself doesn't. I'm told TortoiseSVN does.
On Sun, Nov 21, 2010 at 09:54, Kevin Connor Arpe wrote:
> Hello,
>
> I have a question about version caching. I am using the latest
> (stable) version on both Linux and WinSlows.
>
> As I understand Subversion, once a version is committed, basically it
> can never changed.
Greetings, Kevin Connor Arpe!
> I have a question about version caching. I am using the latest
> (stable) version on both Linux and WinSlows.
> As I understand Subversion, once a version is committed, basically it
> can never changed. A version is written in stone.
> If that
Hello,
I have a question about version caching. I am using the latest
(stable) version on both Linux and WinSlows.
As I understand Subversion, once a version is committed, basically it
can never changed. A version is written in stone.
If that is true, I was hoping Subversion could cache each
