unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: VC filesets
Date: Mon, 20 Oct 2008 15:55:30 -0400	[thread overview]
Message-ID: <87k5c3f3d9.fsf@cyd.mit.edu> (raw)
In-Reply-To: <200810190808.m9J88HkH019522@mothra.ics.uci.edu> (Dan Nicolaescu's message of "Sun, 19 Oct 2008 01:08:17 -0700 (PDT)")

Dan Nicolaescu <dann@ics.uci.edu> writes:

> Chong Yidong <cyd@stupidchicken.com> writes:
>
>   > I'm currently updating the Emacs manual, and I need someone to clarify
>   > how VC filesets work in the new VC.
>   > 
>   > If the current buffer is in a version controlled file, does the default
>   > VC fileset ALWAYS consist of just that one file?  
>
> Yep.  
> (in case you want to look at the details, the function that deals with
> this is vc-deduce-fileset).

That's what I thought.

But in that case, what's the meaning of this paragraph in files.texi?
It seems to be saying that `C-x v v' automatically DTRT outside of VC
dir mode by including the file in a changeset.

     If you are accustomed to earlier versions of VC, the change in
  behavior you will notice is in the directory mode.  Other than
  @kbd{C-x v v}, most VC-mode commands once operated on only one file
  selected by the line the cursor is on.  The change in the behavior of
  @kbd{C-x v v} outside VC Directory Mode is more subtle.  Formerly it
  operated in parallel on all marked files, but did not pass them to the
  version-control backends as a group.  Now it does, which enables VC to
  drive changeset-based version-control systems.




  reply	other threads:[~2008-10-20 19:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-19  3:07 VC filesets Chong Yidong
2008-10-19  8:08 ` Dan Nicolaescu
2008-10-20 19:55   ` Chong Yidong [this message]
2008-10-21  0:30     ` Dan Nicolaescu
2008-10-19 20:43 ` Glenn Morris
2008-10-19 21:35   ` Drew Adams
2008-10-20  5:24     ` Richard M. Stallman
2008-10-20  6:04       ` Drew Adams

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=87k5c3f3d9.fsf@cyd.mit.edu \
    --to=cyd@stupidchicken.com \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@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).