[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: multiple definitions of the term "fileset"
From: |
Eric S. Raymond |
Subject: |
Re: multiple definitions of the term "fileset" |
Date: |
Thu, 11 Oct 2007 08:15:09 -0400 |
User-agent: |
Mutt/1.5.15+20070412 (2007-04-11) |
Richard Stallman <address@hidden>:
> You added a lot of text in files.texi which talks about "filesets" in
> connection with version control. This causes a problem because the
> term "fileset" is already used in a different way. Search files.texi
> for address@hidden Filesets'. (I warned you about this clash a few months
> ago.)
I replied at the time that the term 'fileset' is *not* in fact used in a
different way, though the filesets themselves are.
In both cases, the term 'fileset' refers to a list of files used as
the implied scope for a group of operations of interest. What differs
is only the operations of interest: in VC they are about version
control, onder the Filesets node they are visiting and search/replace.
The parallelism in terminology is not a bug, it's a feature. Same
concept, same term. To invent a different one would be to multiply
entities beyond necessity.
You didn't reply, so I assumed you either agreed or no longer thought
the case for a distinction strong enough to argue.
> Aside from that, several new node names do not follow our
> usual conventions, and some are too long.
I would be happy to fix these. Are the conventions documented somewhere
you can point me at?
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>