"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > I'll look into that. But what I meant was a folder share that tracked > disk writes. So I could map the network share as a drive and then just > work on it like a local file. Everytime I would write to disk the > server would track the changes, and then automatically delete the > tracked changes when I commit. That way, I would always the most recent > copy of my work, regardless of whether I was on the > laptop/desktop/whereever. It would also give me the freedom to only > commit when I've finished a change worth noting. No more commit -m > "wrong variable name fixed"
You can use webdav. There are some tools that can use webdav as if it was a local disk. The problem would be deleting the intermediate versions, since every "save" would create a new version (I don't see much problem with that, but I dunno what you are planning). With regards to the 'wrong variable name fixed', I see that as a fully valid commit. Why not? > Although, having a local copy shared via openVPN on the dedicated would > almost be the same thing. Provided that I remember to commit often and > then delete the intermediate commits. Why deleting the intermediate commits? ;-) They are part of your development process. What will matter, in the end, will be the tagged versions. > I guess I'm just lazy. Aren't all good programmers lazy as well? ;-) -- Jorge Godoy <[EMAIL PROTECTED]>
