Simple Revision Control
catb.org
Simple Revision Control
1–10 of 179 posts
Re: Simple Revision Control
#2Source at gitorious:
Re: Simple Revision Control
#3Chosen name "src" is quite unfortunate, as it will be a src of confusion.
Re: Simple Revision Control
#4Source at gitorious: https://gitorious.org/src-vcs/
Oh the irony of hosting it on something other than SRC. SMH
Re: Simple Revision Control
#5Source at gitorious: https://gitorious.org/src-vcs/
Oh the irony of hosting it on something other than SRC. SMH
Re: Simple Revision Control
#6Much better link is http://www.catb.org/~esr/src/
Re: Simple Revision Control
#7Earlier quoted context omitted.
Oh the irony of hosting it on something other than SRC. SMH
http://www.catb.org/~esr/src/FAQ.html#self-hosting
From that link:
> Is SRC used to develop itself? No. That would be silly.
From Git's Wikipedia page:
> The development of Git began on 3 April 2005. The project was announced on 6 April, and became self-hosting as of 7 April.
Re: Simple Revision Control
#8I am not entirely sure I understand why one wouldn't use git for this role. If you don't need a remote git repository, you don't need to use one, and git will be available everywhere. Certainly many production machines will tend to have it for deployment of applications across multiple machines.
What are some use cases that don't work with git (which is probably already available on the system)? And why wouldn't git be an effective tool for that particular role?
I'm certainly not as experienced as ESR (though, I'm coming up on 20 years of administering Linux and UNIX servers), and perhaps I'm missing some subtle nuance here. I'm not wanting to come off as "screw this, this is stupid". I'm just genuinely not understanding why I should learn a new tool (or re-learn an old tool that's be "reloaded") when git does all of this and more...and I already know it and have it installed broadly across my systems.
Re: Simple Revision Control
#9Earlier quoted context omitted.
http://www.catb.org/~esr/src/FAQ.html#self-hosting
From that link: > Is SRC used to develop itself? No. That would be silly. From Git's Wikipedia page: > The development of Git began on 3 April 2005. The project was announced on 6 April, and became self-hosting as of 7 April.
You're kinda missing the point: this project is designed around a single user maintaining a linear history for a single file. Using it for a project would be a weird impedance mismatch.
That's not to say I find SRC compelling... in the slightest. Just that you'd never use SRC to track a project.
Re: Simple Revision Control
#10I am not entirely sure I understand why one wouldn't use git for this role. If you don't need a remote git repository, you don't need to use one, and git will be available everywhere. Certainly many production machines will tend to have it for deployment of applications across multiple machines. What are some use cases that don't work with git (which is probably already available on the system)? And why wouldn't git…
You are almost certainly more experienced than ESR. He held his last technology position in the early 1990s.