Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

From CVS to Git, thirty years of source control

evilgeniuslabs.ca

Post reply on HN
Print view View original

11–20 of 67 posts

Re: From CVS to Git, thirty years of source control

#11

Post by eesmith »

zabzonk wrote: post #7

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.

If they had, I wouldn't have switched to Sourcehut, at least not for a while.

Though at some point I would have realized that Atlassian was the wrong fit for my needs as a single-dev, no-AI project and switched.

Re: From CVS to Git, thirty years of source control

#14

Post by ktpsns »

binaryturtle wrote: post #2

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. :)

I loved the simple increasing numbers of Subversion. This was better then CVS "ad-hoc" versioning and also far better then git's hashes. Single numbers are easy for humans. I would love git would make it possible to work that way (there is one way: `git describe` can show something like "v1.0.4-14-g2414721" which means "14 commits ahead of tag v1.0.4".)

Re: From CVS to Git, thirty years of source control

#15

Post by ktpsns »

dn3500 wrote: post #10

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…

That sounds awesome. A bit like plan9 philosophy "everything is a file". I wonder whether one could implement something like this with fuse+git (gitfs doesnt allow this, cf https://gitfs.readthedocs.io/en/stable/mount_options/)

Re: From CVS to Git, thirty years of source control

#17

Post by wvhulle »

dn3500 wrote: post #10

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…

Sounds like the “jj edit” command.

Re: From CVS to Git, thirty years of source control

#18

Post by zabzonk »

KingOfCoders wrote: post #13

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.

Re: From CVS to Git, thirty years of source control

#19

Post by zabzonk »

voxadam wrote: post #16
raverbashing wrote: post #8

Earlier quoted context omitted.

In a retirement home? /s

Where does that leave the SCCS people?

Killed themselves after using it for fifteen minutes. I used to have to teach a commercial "Intro to Unix" course which had a section on SCCS - shudder!

Re: From CVS to Git, thirty years of source control

#20

Post by myaccountonhn »

dn3500 wrote: post #10

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…

With a thin layer of tooling, you could probably build a zfs CVS very easily. There's zfs send and each version is available under .zfs so you could use the patch/diff tool to see different versions and restore to older versions.
Post reply on HN