1 |
On 03/04/10 10:35, Ciaran McCreesh wrote: |
2 |
> On Thu, 4 Mar 2010 10:32:47 +0100 |
3 |
> Ulrich Mueller <ulm@g.o> wrote: |
4 |
>>>>>>> On Thu, 4 Mar 2010, Christian Faulhammer wrote: |
5 |
>>> My proposal would be to call it dev-scm and put all version |
6 |
>>> controls, direct frontends, plugins and the like into that. |
7 |
|
8 |
I like the idea, +1 from me |
9 |
|
10 |
|
11 |
>> Better call it dev-vcs to avoid confusion with both the Scheme |
12 |
>> language and with software configuration management. |
13 |
|
14 |
Agreed, "scm" is a bad choice. |
15 |
|
16 |
|
17 |
> And this is why the move wasn't done five years ago: by the time we'd |
18 |
> worked out everything we'd need to do by hand because epkgmove was |
19 |
> broken, the whole thing got bikeshedded to death. |
20 |
|
21 |
So that's a great chance for all of us to prove we can do better this |
22 |
time. We have at least two more names in the pool: |
23 |
|
24 |
VCS = version control system/software |
25 |
RCS = revision control system/software |
26 |
|
27 |
The former seems more common to me though the second seems prefered in |
28 |
wikipedia: |
29 |
- "Version_control" forwards to "Revision control" |
30 |
- "Comparison of revision control software" |
31 |
http://en.wikipedia.org/wiki/Comparison_of_revision_control_software |
32 |
|
33 |
I'd still propose "dev-vcs", unless someone spots something bad about it. |
34 |
|
35 |
|
36 |
|
37 |
Sebastian |