unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rms@gnu.org
Cc: Juri Linkov <juri@jurta.org>, esr@thyrsus.com, emacs-devel@gnu.org
Subject: Re: Another VC terminology change?
Date: Mon, 15 Oct 2007 13:42:49 -0400	[thread overview]
Message-ID: <jwvabqk2sc6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1IhSPx-0007rz-Vj@fencepost.gnu.org> (Richard Stallman's message of "Mon\, 15 Oct 2007 12\:03\:45 -0400")

>     Isn't filesets.el similar by its functionality to the recently proposed
>     project.el?

> Isn't project.el the facility that lets you specify local bindings for
> a directory?

> fileset.el does a lot more than that.  They are not similar.

>     As for the VC terminology, in contexts where the term "filesets" is
>     ambiguous, it is possible to disambiguate it by using "VC filesets".

> That is better than what we have now, but still rather clumsy,
> so it is not a good solution.  We need a better one.

I think we don't want to restrict the term "file set" to the specific one
corresponding to filesets.el.  Instead, we want to keep it as a fairly
abstract concept, with uses in filesets and VC and other packages
(project.el comes to mind although it doesn't refer to it explicitly).

So, I'd distinguish between "file set" as the general concept, and "VC
fileset" and (filesets.el's) "Fileset" as specific instantiations.


        Stefan

  reply	other threads:[~2007-10-15 17:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 14:30 Another VC terminology change? Eric S. Raymond
2007-10-11 17:25 ` Stefan Monnier
2007-10-11 18:05   ` Eric S. Raymond
2007-10-11 20:08     ` Stefan Monnier
2007-10-11 20:19       ` Eric S. Raymond
2007-10-12  1:06         ` Stefan Monnier
2007-10-12  0:45   ` Dan Nicolaescu
2007-10-12  1:08     ` Stefan Monnier
2007-10-12 15:23       ` Dan Nicolaescu
2007-10-12 16:25         ` Stefan Monnier
2007-10-12 16:47           ` Dan Nicolaescu
2007-10-12 17:34             ` Stefan Monnier
2007-10-12 21:28               ` Dan Nicolaescu
2007-10-13  3:36                 ` Stefan Monnier
2007-10-11 17:40 ` Richard Stallman
2007-10-11 17:50   ` Eric S. Raymond
2007-10-12  8:24     ` Eli Zaretskii
2007-10-12 15:59     ` Richard Stallman
2007-10-12 20:02       ` Miles Bader
2007-10-13  6:41         ` Richard Stallman
2007-10-14 21:42           ` Juri Linkov
2007-10-15 16:03             ` Richard Stallman
2007-10-15 17:42               ` Stefan Monnier [this message]
2007-10-15 21:37                 ` Eric S. Raymond
2007-10-18 20:08                 ` Richard Stallman
2007-10-19 21:42                   ` Eric S. Raymond
2007-10-21  7:27                     ` Richard Stallman
2007-10-12  8:14 ` Eli Zaretskii

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=jwvabqk2sc6.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    --cc=juri@jurta.org \
    --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).