From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: esr@thyrsus.com, emacs-devel@gnu.org
Subject: Re: Another VC terminology change?
Date: Fri, 12 Oct 2007 12:25:33 -0400 [thread overview]
Message-ID: <jwvy7e85ml4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <200710121523.l9CFNpOG008776@oogie-boogie.ics.uci.edu> (Dan Nicolaescu's message of "Fri\, 12 Oct 2007 08\:23\:51 -0700")
>> >> Not about "checkout" which sometimes means "update" and sometimes "get".
>> > Speaking of "update", vc-update needs to be rethought a bit.
>> > Mercurial, bzr and git (maybe other systems too) don't seem to want to
>> > do merges based on a file, but on changesets.
>> > What should we do about that?
>>
>> Those backends should simply signal an error if requested to update
>> something less than the whole tree.
> So what would the UI be for that?
You mean API rather than UI, right?
> vc-BACKEND-merge-news currently has a `file' parameter.
> Should backends check if it is a directory, and then run the merge
> command?
Those backends which can only perform such operations on whole trees, should
(obviously) check that the parameter refers to a whole tree and signal an
error if it doesn't.
> Who is responsible for updating all the buffers for files that have
> been changed by the merge?
VC. The backend should return a list of files that were updated (maybe
together with their new status?), and then vc.el will be in charge of
reverting the corresponding buffers (and update the relevant vc-dired
buffers, ...).
Stefan
next prev parent reply other threads:[~2007-10-12 16:25 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 [this message]
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
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=jwvy7e85ml4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
/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).