From: Stefan Monnier <monnier@iro.umontreal.ca>
To: 737@emacsbugs.donarmstrong.com
Subject: bug#737: vc-dir reports unregistered-then-deleted file is "up-to-date"
Date: Wed, 07 Jan 2009 00:33:45 -0500 [thread overview]
Message-ID: <tg4p0bhrxa.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <200810050104.m9514rDt028153@mothra.ics.uci.edu> (Dan Nicolaescu's message of "Sat, 4 Oct 2008 18:04:53 -0700 (PDT)")
> 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.
Note also that this behavior is maybe inconsistent with tkCVS and
cvs-examine, but it's not only consistent with cvs-quickdir but also
it's consistent with vc-dir used on Arch, Git, Bzr, Hg, ...
Stefan
prev parent reply other threads:[~2009-01-07 5:33 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
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 [this message]
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=tg4p0bhrxa.fsf@fencepost.gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=737@emacsbugs.donarmstrong.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 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.