61–67 of 67 posts
Earlier quoted context omitted.
Yes but the .svn dirs everywhere keep being annoying
Since Subversion 1.7 (2011), working copies only use a single .svn directory at the top level.
My first contact was VMS with its versioning file system. Then RCS - before that we copied zip files around.
I was convinced that VMS's versioned files thing was DEC's cunning plan to sell more disk drive space (though I didn't and still don't know what the underlying mechanism was) - I was quite glad when I learned how to turn it off, though.
I sometimes wonder what would have happened if Atlassian had stuck with Mercurial support on Bitbucket - I don't think they can pretend that switching to git did very much for them. I love(d) Mercurial, and particularly TortoiseHg integration on Windows.
They said (I recall) that Mercurial was driven by a single person and when they left there was no one willing to fight for it.
I still miss it too. We need a better git. For a while I thought it might be jj but it turns out it’s just as full of arcane commands as git is.
I use Subversion w/o a server too. You can have your repositories locally (file:///Path/to/repository). All my own (single man) projects are in local SVN repositories. For my use case git is just too much extra friction, and I still love to have my one single unique global revisions number that is linearly increasing with each commit. :)
Ironically, GitHub became popular because it gave everyone a centralized repo—exactly the thing people liked about SVN.
Earlier quoted context omitted.
Ironically, GitHub became popular because it gave everyone a centralized repo—exactly the thing people liked about SVN.
It's so weird. Git's major differentiating feature is that its distributed nature means you don't need a centralized server, and your work isn't blocked if that (unneeded) centralized server goes down. Yet, so many developers have twisted git around to make it a centralized single point of failure--on purpose! I don't understand it.
There were several proprietary systems in the late 1980s and early 1990s. The one I remember was DSEE from Apollo Computer. It was integrated with the file system such that commits and branches worked like zfs snapshots. You could just "cd" to whatever tag, branch, or individual commit you wanted. No checkouts required. Very cool, I wish we still had that today. DSEE was spun off as Clearcase, acquired by IBM, then I…
Earlier quoted context omitted.
Sounds like the “jj edit” command.
Its not