From 46254eb5bd67af3963fcb2a755aaade2ebe2cc4b Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Wed, 12 Nov 2014 00:34:18 -0500 Subject: [PATCH] Polishing. --- FAQ.asc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/FAQ.asc b/FAQ.asc index 249e207..5df2a12 100644 --- a/FAQ.asc +++ b/FAQ.asc @@ -11,7 +11,7 @@ file you are reading now. There is even a good use-case for small programs and scripts. Do you presently keep your ~/bin contents under version control? If not, consider using SRC for them. -== XYZ already does single-file version control, why another one? == +== $VCS already does single-file version control, why another one? == It is true, other VCSes already fulfill this simple criterion, SCCS and RCS being some of the earliest examples dating back to the 1970s and @@ -61,7 +61,7 @@ named like .hg or .git). Scripts to impose a single-file concept on top of these systems do not go far enough with respect to the reasons SRC exists. -== Is SRC a good system to learn about version control? == +== Is SRC a good system on which to learn about version control? == YES! SRC is explicitly designed to have the bare-bones features and commands of a modern version control system. Keep in mind that SRC’s -- 2.43.0