all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: 737@emacsbugs.donarmstrong.com
Subject: bug#737: vc-dir reports unregistered-then-deleted file is "up-to-date"
Date: Sat, 4 Oct 2008 19:24:11 -0700 (PDT)	[thread overview]
Message-ID: <200810050224.m952OBGw028267@mothra.ics.uci.edu> (raw)
In-Reply-To: <sjiqs76dbn.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 04 Oct 2008 21:27:40 -0400")

Glenn Morris <rgm@gnu.org> writes:

  > Dan Nicolaescu wrote:
  > 
  > > Do you use a CVS server or a local repository? 
  > 
  > A server (namely the Emacs server).

vc-cvs.el version 1.150 works for me with the emacs CVS server (as
annonymous user)

  > > I saw you checked in something to do with that, and now the default
  > > behavior for vc-dir is inconsistent with PCL-CVS and tkcvs (and probably
  > > all other CVS GUIs): if a file needs merging it says "edited" instead of
  > > "needs-merging", if it needs updating it says nothing.
  > 
  > Those states are impossible (?) to determine without contacting the
  > server. Presumably such inaccuracies are the price people who use
  > stay-local are willing to accept.
  > 
  > It sounds like you want vc-dir to ignore vc-stay-local, which I would
  > suggest is something that needs documenting. 

I just don't think it should be the default.  I do think that it's
fundamentally broken, so I don't want to have anything to do with it.

  > Or introduce a vc-dir-stay-local, default nil?

I'd prefer it *stay-local would not pollute vc-dir.el, none of the
modern VC systems needs it, so there's no good reason to deal with it in
the future.






  parent reply	other threads:[~2008-10-05  2:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17 21:12 bug#737: vc-dir reports unregistered-then-deleted file is "up-to-date" Bob Rogers
2008-10-03  1:46 ` Glenn Morris
2008-10-03  5:19   ` Dan Nicolaescu
2008-10-03  7:07     ` Glenn Morris
2008-10-03 19:06       ` Dan Nicolaescu
2008-10-04  5:38   ` Dan Nicolaescu
2008-10-05  0:44     ` Glenn Morris
2008-10-05  1:04       ` Dan Nicolaescu
2008-10-05  1:27         ` Glenn Morris
2008-10-05  1:45           ` Glenn Morris
2008-10-05  2:01             ` Glenn Morris
2008-10-05 15:40               ` Dan Nicolaescu
2008-10-05 23:47                 ` Glenn Morris
2008-10-05  2:24           ` Dan Nicolaescu [this message]
2008-10-05  2:10             ` Nick Roberts
2008-10-05 23:43             ` Glenn Morris
2008-10-06  0:33               ` Dan Nicolaescu
2008-10-06  6:26                 ` Nick Roberts
2008-10-06  7:33                 ` Glenn Morris
2008-10-06  7:53                   ` Dan Nicolaescu
2008-10-06  9:12                     ` Nick Roberts
2008-10-08  7:43                       ` Glenn Morris
2008-10-09  4:52                         ` Dan Nicolaescu
2008-10-10  1:39                           ` Glenn Morris
2009-01-07  5:30                           ` Stefan Monnier
2009-01-07 19:35                             ` Dan Nicolaescu
2009-01-08 16:44                               ` Stefan Monnier
2008-10-05  2:17         ` Nick Roberts
2009-01-07  5:33         ` Stefan Monnier

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=200810050224.m952OBGw028267@mothra.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=737@emacsbugs.donarmstrong.com \
    --cc=rgm@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.