all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Tim Van Holder" <tim.vanholder@gmail.com>
To: emacs-devel@gnu.org
Subject: 23.0.60; new vc-status interface: no more multi-file commits?
Date: Fri, 11 Apr 2008 17:42:07 +0200	[thread overview]
Message-ID: <d69e7f6a0804110842r324da9eat909969d73e5b20f8@mail.gmail.com> (raw)

With todays CVS build, it looks like there is a new interface for C-x
v d; in itself that is quite nice (especially since it also lists
removed files, which the previous system never did, at least not for a
CVS backend).
However, it looks like one main functionality is omitted from this,
namely the ability to commit files directly (i.e. the old v-v action
in VC-under-dired; not that big a deal for a CVS backend, but with
changeset-based systems like svn/git that would seem to be a serious
lack, not to mention that it directly contradicts the information in
NEWS).

As an aside, is there a way to cleanly abort a long-running background
status update? I briefly checked the behaviour of vc-status on a tree
with svn backend; it also seemed to lack the ability to commit changed
files. On top of that, the retrieving of the status info uses a
background process; in the case of the tree I was using (a gcc
checkout), that process is quite slow, and there did not seem to be an
obvious way to cancel it. C-g did nothing (since it's a background
process), and when it finished after I had killed the vc-status buffer
I received a 'selecting deleted buffer' error.




             reply	other threads:[~2008-04-11 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 15:42 Tim Van Holder [this message]
2008-04-11 16:13 ` 23.0.60; new vc-status interface: no more multi-file commits? Dan Nicolaescu
2008-04-11 18:56   ` Tim Van Holder
2008-04-14  9:13     ` Dan Nicolaescu

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d69e7f6a0804110842r324da9eat909969d73e5b20f8@mail.gmail.com \
    --to=tim.vanholder@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.