From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: vc-status vs pcl-cvs Date: Thu, 05 Jun 2008 07:39:29 -0700 Message-ID: <200806051439.m55EdUWk020840@sallyv1.ics.uci.edu> References: <4845BA20.3070804@gnu.org> <18502.728.743890.14466@kahikatea.snap.net.nz> <18502.12890.517998.506464@kahikatea.snap.net.nz> <200806041601.m54G11P4004695@sallyv1.ics.uci.edu> <200806041754.m54HsYjL029738@sallyv1.ics.uci.edu> <200806050308.m5538Ybf017852@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1212683242 6581 80.91.229.12 (5 Jun 2008 16:27:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 5 Jun 2008 16:27:22 +0000 (UTC) Cc: Nick Roberts , Sam Steingold , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 05 18:28:01 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K4IJk-0006iU-WA for ged-emacs-devel@m.gmane.org; Thu, 05 Jun 2008 18:28:01 +0200 Original-Received: from localhost ([127.0.0.1]:37143 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K4IIy-0006g1-7Z for ged-emacs-devel@m.gmane.org; Thu, 05 Jun 2008 12:27:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K4IIT-0006UC-Be for emacs-devel@gnu.org; Thu, 05 Jun 2008 12:26:41 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K4IIQ-0006T6-U4 for emacs-devel@gnu.org; Thu, 05 Jun 2008 12:26:39 -0400 Original-Received: from [199.232.76.173] (port=33577 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K4IIQ-0006T1-PO for emacs-devel@gnu.org; Thu, 05 Jun 2008 12:26:38 -0400 Original-Received: from mx20.gnu.org ([199.232.41.8]:3529) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K4H3g-00051Y-Nh; Thu, 05 Jun 2008 11:07:20 -0400 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K4Gdo-0002UK-HQ; Thu, 05 Jun 2008 10:40:36 -0400 X-ICS-MailScanner-Watermark: 1213281571.03786@3+uYhjKhefb7Q5H+STt3AA Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m55EdUWk020840; Thu, 5 Jun 2008 07:39:30 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Thu, 05 Jun 2008 00:36:15 -0400") Original-Lines: 30 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.363, required 5, autolearn=disabled, ALL_TRUSTED -1.44, TW_BZ 0.08) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by mx20.gnu.org: Solaris 10 (beta) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:98469 Archived-At: Stefan Monnier writes: > >> Which is indeed all the info you'll ever get from all other VCSes. > >> Their `vc-dir' command will never tell you "needs-update" either. > > > But the state those backends show in vc-dir is accurate, and you can > > just check things in without a problem. > > Not necessarily. With Bazaar, if you do a "checkout" > (i.e. a bound-branch: your local branch is bound to some other branch; > commits go to both places), then bzr commit may fail if you haven't > first updated your local branch to the latest revision on the > upstream branch. > > Of course, with CVS the problem is also present if you use cvs-status: > the returned state may be "accurate" when you receive it, but it can > change before you do the commit. Well, that's always the case for any shared system, isn't it? So there's no real reason to mix that in this discussion. > > If things go the way you are proposing, how do you get the up to date > > state so you can actually check in your changes? Another command? > > Yes, a command we absolutely need anyway: vc-pull. We do need the vc-pull command, but we don't need it for CVS _by default_. Sure, it could be used for CVS, but that is not the normal workflow for CVS, so it would just confuse our users. And while the implementation of vc-cvs-stay-local is trivial, vc-pull is not.