From: Paul Michael Reilly <pmr@pajato.com>
To: rms@gnu.org
Cc: esr@thyrsus.com, emacs-devel@gnu.org
Subject: Re: filesets
Date: Mon, 22 Oct 2007 01:59:59 -0400 [thread overview]
Message-ID: <471C3C5F.3050206@pajato.com> (raw)
In-Reply-To: <E1IjVCi-0008Rq-QZ@fencepost.gnu.org>
Richard Stallman wrote:
> I saw the changes that you made in files.texi to try to distinguish
> the two uses of "fileset". In effect, those changes tell the reader,
> "please be aware of this ambiguity and cope with it". That does not
> solve the problem. What is needed is to remove the ambiguity.
>
> One way to do this is to find TWO modifiers. One concept could be "VC
> fileset" and the other could be "XYZ fileset". I can't think of a
> suitable word to use in place of XYZ; can anyone else?
>
> The other way is to rename one of these concepts entirely. Renaming
> the VC one is better since it is new, and thus not an incompatible
> change.
Coming up with a solution to what "XYZ" should be is the optimal
solution IMHO since it solves the problem in such a way that the next
notion of filesets does not encounter this dilemma. But I don't have
any good ideas for XYZ either. If I owned this issue, I would change
"VC fileset" to "VC sourceset" and beg the problem for a while.
-pmr
next prev parent reply other threads:[~2007-10-22 5:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 7:26 filesets Richard Stallman
2007-10-21 12:56 ` filesets Robert J. Chassell
2007-10-21 13:33 ` filesets Miles Bader
2007-10-21 14:01 ` filesets Stefan Monnier
2007-10-21 16:15 ` filesets Robert J. Chassell
2007-10-21 23:46 ` filesets Miles Bader
2007-10-22 9:00 ` filesets Richard Stallman
2007-10-22 12:15 ` filesets Robert J. Chassell
2007-10-22 5:59 ` Paul Michael Reilly [this message]
[not found] <20071021192054.AD7BE7393E@grelber.thyrsus.com>
2007-10-22 13:36 ` Emacs-devel Digest, Vol 44, Issue 176 Eric S. Raymond
2007-10-22 14:45 ` Miles Bader
2007-10-22 19:01 ` Eric S. Raymond
2007-10-22 21:52 ` filesets Robert J. Chassell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=471C3C5F.3050206@pajato.com \
--to=pmr@pajato.com \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).