aboutsummaryrefslogtreecommitdiffstats
path: root/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/427e0ca7-17f5-4a5a-8c68-98cc111a2495/comments/29ad0d9e-c05b-4793-bb8b-e8bf237f51b3/body
blob: e39beb0bd827a5f9d6329b88f235692c5f43be26 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
> Currently, the code and interface of Bugs Everywhere speaks loosely
> about the term “RCS”. Sometimes it means “revision control system”
> referring in general to these types of system, and sometimes it talks
> about GNU RCS, a specific system.

I don't think we ever rever to GNU RCS.  Our current libbe.rcs.RCS
default implementation is a "don't version" backend for BE, but
perhaps this is what you're refereing to.

> I propose that “Version Control System” (“VCS”) has emerged as a
> consensus term to refer to such systems in general, with no specific
> reference to any particular system.

Fair enough.

> This will change some interface (e.g. the ‘rcs_name’ configuration
> setting, and some of the methods on objects), but making this change
> while Bugs Everywhere is small will be much less painful than making it
> later.

Hmm, we really need a method for upgrading the on-disk BugDir version.
It's hard when you need to maintain backwards compatibilty with
earlier versions in the VCS history....