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 changed. A version is written
In Subversion 1.7, text-bases are stored in a SHA-1-keyed store (as
opposed to a pathname-based store in 1.6 and earlier), and the "old"
text-base aren't always removed as soon as there is no working copy file
corresponding to them. (I tried committing a file in one wc and
updating that file in an
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. A version is written i
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 is true, I was hop
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 v
