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

Version control without Git

itoshkov.github.io

Post reply on HN
Print view View original

31–40 of 68 posts

Re: Version control without Git

#31

Post by detaro »

da_chicken wrote: post #26
_hilro wrote: post #6

Title is horribly incorrect. Simulating git would be more appropriate. I expected this to be a look at other version control systems around today. It's yet another 'let's recreate git from scratch, kinda' post.

> It's yet another 'let's recreate git from scratch, kinda' post. I don't think that's what it's doing. It's just trying to explain what git does through analogy and example. A remarkable number of people never grok that git is basically just a version control repository for source code (checkout/commit) that itself has been checked into a version control repository for VC repositories (pull/push). There's lots of re…

> Did you ever notice that after git became popular that colleges started to teach CS students to use version control?

Not really, no. Theory-focussed ones still might not. Practical ones did already teach Subversion etc. Some teach git by teaching the full logic behind it, others as "here's some basic commands you need, everything else is on you if you want to learn it, you won't need it to pass".

Re: Version control without Git

#32

Post by [deleted] »

_hilro wrote: post #6

Title is horribly incorrect. Simulating git would be more appropriate. I expected this to be a look at other version control systems around today. It's yet another 'let's recreate git from scratch, kinda' post.

[deleted]

Re: Version control without Git

#34

Post by sitzkrieg »

TomMasz wrote: post #24

There's no question git is overkill for individual projects but it doesn't take long to learn the add/commit/push commands you'll most often use. But there's nothing wrong with wanting to build your own tools.

disagree, its very useful for individual projects where lots of exploration and bouncing around can happen

Re: Version control without Git

#35

Post by coldcode »

I remember back in the 80's and early 90's using a shared file system and discipline for my team to build large Mac apps without one (there were none available). Clearly today no one in their right mind would do this.

Re: Version control without Git

#36

Post by travisgriggs »

I thought this was cute. I (mostly?) “get” git. At least all of what was shown was formerly known to me.

I would have added a section about how keeping the commit numbers straight is a a pain and then demonstrated how we could just index them with a hash (md5sum or similar).

I thought about sharing this tutorial(?) with some of my “git is kinda fuzzy” colleagues, but I realized that they often seem fuzzy in the basic file tree navigation layers and this expose’ relies on a good degree of comfort with “file ops”.

I find that less experienced developers are often less than strong when it comes to basic “file ops” now days. I blame IDEs, black box build tools, etc.

Re: Version control without Git

#37

Post by ogogmad »

travisgriggs wrote: post #36

I thought this was cute. I (mostly?) “get” git. At least all of what was shown was formerly known to me. I would have added a section about how keeping the commit numbers straight is a a pain and then demonstrated how we could just index them with a hash (md5sum or similar). I thought about sharing this tutorial(?) with some of my “git is kinda fuzzy” colleagues, but I realized that they often seem fuzzy in the basic…

The use of `diff` and `patch` to express merge is something interesting that I only learned from reading this article.

Re: Version control without Git

#38

Post by zoomablemind »

KingOfCoders wrote: post #13

Coming from RCS, CVS, SVN to Git, git is a game changer - yes everyone knows that. But what was astonishing me most was the version system build into the VMS OS file system.

> ...version system build into the VMS OS file system.

That was more of "versioning" than "version control" system. It simply automated the sequential numbering of the saved instances of a file. The versions were not deltas, just normal files, the version number being part of file specification:

name.ext;ver

As much as one can do with versions was diff, purge and file operations, basically, no change annotation or higher level grouping. But being files, the versions allowed to see the what-who-when changed. No why. Still this probably was convenient in some use-cases and as an immediate file backup.

As for the real version control system on OpenVMS, one of such was called CMS, part of DECset suite. I believe it was of exclusive-check-out/check-in kind, similar to how it's done with, say, CVS, but absolutely not like CVS otherwise. For example, there was no support for directories in the repository.

I guess these days it may be possible to run Git on OpenVMS too.

Re: Version control without Git

#39

Post by thomascgalvin »

TomMasz wrote: post #24

There's no question git is overkill for individual projects but it doesn't take long to learn the add/commit/push commands you'll most often use. But there's nothing wrong with wanting to build your own tools.

How is it overkill? I already have it installed on my machine, I already have an account on GitLab/GitHub/Whatever, and I already know the commands I need to do close to 100% of my day to day work.

Are there features of Git that I won't use? Sure. There are also features of IntelliJ that I don't use, but that doesn't make it overkill for my hobby code.

Re: Version control without Git

#40

Post by cjwoodall »

I once made something very similar for myself in College when I was told not to use git for something in a lab… so my solution was to automate making archives. It worked ok. Definitely helped me appreciate git. Now a days i would have just used git and released archives to the rest of the org
Post reply on HN