21–30 of 68 posts
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.
File versioning was in BBN's TENEX, which evolved into TOPS-20 ("TWENEX") for DEC's DECSYSTEM 20 computers. File versioning is also part of pathnames in Common Lisp, although it (the versioning, not Common Lisp) is really a fossil at this point.
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.
This is more of a "hey, we have these tools on our system and can use them to simulate git". That's somehow different, at least from my pov.
Earlier quoted context omitted.
I think a closer example at the filesystem level would be rsnapshot alpha rsnapshot [1] uses hard links when it can to create a delta of changed files. Reverting can be done with rsync or cherry picking files. git blame would have to be done via something like auditd and syslog and nowhere near as easy as using git. I use rsnapshot to back up my git repos in the event they get corrupted. [1] - https://linux.die.net/m…
Probably rsync is smarter than my cp -rp example. Folk who are downvoting my original comment really don't understand how git version controls at the atomic level.
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.
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 reasons for it doing that, most of which are grounded in the fact that lots of developers only learn just enough VC to satisfy their immediate coworkers, and otherwise treat it like a magic black box.
Did you ever notice that after git became popular that colleges started to teach CS students to use version control? Ever think about why that might be?
Earlier quoted context omitted.
These are tools you'd need to write atop the version dirs.
So you can't really then simulate git with: mkdir v2 ; cp -rp v1 v2 can you?
Am I missing something or why does the author repeatedly misspell —recursive as —recusive?
mv ../ProjectX-v0.zip repo/commits/c0.zip
mv ../ProjectX-v1.zip repo/commits/c1.zipTitle 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…
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…
Because schools have recognized the need to teach some pragmatic tools in addition to pure theory?
I had a "tools" class in undergrad 15 years ago. Learned shell, perl, pcre regexes, make, cvs, subversion, etc. They created the class due to the perception of new-grads being unable to use real-world tools to do real work. Since then, many schools have adopted a similar approach: either a dedicated class or treating many classes as "project"-style classes that use real-world toolsets and SDLCs.