From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Dan Nicolaescu <dann@gnu.org>,
Chong Yidong <cyd@stupidchicken.com>,
emacs-devel@gnu.org
Subject: Re: vc-update for bzr etc.
Date: Mon, 22 Nov 2010 09:39:58 -0500 [thread overview]
Message-ID: <jwvpqtx8lvl.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87k4k6c738.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Mon, 22 Nov 2010 13:31:23 +0900")
>> VC tries to present a uniform UI and that is good, but trying to impose
>> a uniform semantics to all commands is asking too much. So I think it's
>> perfectly OK for vc-pull/update to do "bzr pull" for Bzr and
>> "git pull" for Git, even if they don't do exactly the same thing.
> bzr pull -- synchronize branch to parent exactly, never does a
> non-trivial merge, sometimes operates on a non-local
> branch and not on the workspace IIRC.
> git pull -- merges branch into workspace, commits unless conflict,
> never affects a branch outside of the workspace.
> hg pull -- fetches branch, never updates workspace or affects a
> branch outside of the workspace.
> I don't see the point of having a single command whose implementation
> can vary so randomly.
That's OK: "cvs pull" is even further from the above, so my suggestion
is not to "just pass `pull' to the backend command" but "run the normal
command to update the current tree by bringing in changes from
upstream". Based on what you say, vc-pull for Mercurial would not just
do "hg pull" but something more.
Stefan
next prev parent reply other threads:[~2010-11-22 14:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 15:43 vc-update for bzr etc Chong Yidong
2010-11-21 17:00 ` Andreas Schwab
2010-11-21 17:09 ` Dan Nicolaescu
2010-11-21 17:33 ` Chong Yidong
2010-11-21 20:20 ` Stefan Monnier
2010-11-21 21:08 ` Chong Yidong
2010-11-22 2:04 ` Stefan Monnier
2010-11-22 4:31 ` Stephen J. Turnbull
2010-11-22 8:40 ` Thien-Thi Nguyen
2010-11-22 11:04 ` Stephen J. Turnbull
2010-11-22 14:39 ` Stefan Monnier [this message]
2010-11-22 17:29 ` Chong Yidong
2010-11-23 15:37 ` Stephen J. Turnbull
2010-11-23 16:20 ` Stefan Monnier
2010-11-22 4:35 ` Chong Yidong
2010-11-22 6:52 ` Dan Nicolaescu
2010-11-22 14:42 ` Stefan Monnier
2010-11-22 10:54 ` Eli Zaretskii
2010-11-22 14:41 ` Stefan Monnier
2010-11-23 1:40 ` Chong Yidong
2010-11-23 14:27 ` Stefan Monnier
2010-11-23 16:08 ` Chong Yidong
2010-11-23 17:03 ` Dan Nicolaescu
2010-11-23 17:02 ` Dan Nicolaescu
2010-11-23 19:29 ` Chong Yidong
2010-11-23 22:05 ` Stefan Monnier
2010-11-23 22:34 ` Dan Nicolaescu
2010-11-24 17:19 ` Chong Yidong
2010-11-22 16:57 ` Chong Yidong
2010-11-22 17:59 ` Eli Zaretskii
2010-11-21 19:03 ` Stefan Monnier
2010-11-21 19:34 ` Chong Yidong
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=jwvpqtx8lvl.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=dann@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).