unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 62693@debbugs.gnu.org, ocert.dev@free.fr
Subject: bug#62693: 28.2; VC: CVS: Fix lost file reporting and enable reverting it
Date: Sat, 15 Apr 2023 12:28:47 +0300	[thread overview]
Message-ID: <83y1mtcx4g.fsf@gnu.org> (raw)
In-Reply-To: <b7d1e6b9-4a12-0423-afad-d746dbd3e0de@gutov.dev> (message from Dmitry Gutov on Sat, 15 Apr 2023 01:59:28 +0300)

> Date: Sat, 15 Apr 2023 01:59:28 +0300
> Cc: 62693@debbugs.gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
> 
> On 13/04/2023 19:40, Olivier Certner wrote:
> > Hi,
> > 
> > Thanks for looking at this.
> > 
> >> - Could you explain what kind of files are not listed and when? I'm
> >> guessing this has to do with the file name? I've tried to reproduce the
> >> problem with a file name that contained a space, and couldn't see it.
> > 
> > It's not that files are not listed, they are so always. As said, the problem
> > is their name. For example, if I remove an INSTALL file in a repository,
> > `INSTALL' is the name listed in a VC dir buffer, *quotes included*. Then, no
> > VC operation can work because there is indeed no file by this name (with
> > quotes, both in the filesystem or known by CVS).
> 
> So the actual file name is not the problem -- the problem happens with 
> removed files?
> 
> Okay, I can see that now: when the file is removed, it's displayed 
> (incorrectly) with quotes around its name. Patches 2 and 3 do fix the 
> remove - vc-dir - vc-revert scenario.
> 
> Eli, do we want these fixes in emacs-29? These are again not 
> regressions, but I'm guessing users of CVS are foremost to benefit from 
> adding this to the upcoming release.

The patch is AFAICS basically a complete rewrite of an important
function, so I don't see how I could agree applying this to the
release branch.  Sorry.  (Was the introduction of so many CL-isms
really necessary, btw?)

As a minor nit, please don't use "path" or "PATH" for anything except
$PATH-style lists of directories, as GNU Coding Standards frown on
such use of this word.  We use "file name" or "directory name" or
"leading directories" (as the case may be) instead.

> Regarding the new patch, it's great to see the list of examples, but 
> could you instead move it to a test or several inside 
> test/lisp/vc/vc-cvs-tests.el? This file does not exist yet, but you can 
> use vc-git-test.el as an example, in the same directory.

Yes, having a test for this would be most welcome.





  reply	other threads:[~2023-04-15  9:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06  9:51 bug#62693: 28.2; VC: CVS: Fix lost file reporting and enable reverting it Olivier Certner
2023-04-12 22:48 ` Dmitry Gutov
2023-04-13 16:40   ` Olivier Certner
2023-04-14 22:59     ` Dmitry Gutov
2023-04-15  9:28       ` Eli Zaretskii [this message]
2023-04-17  9:24         ` Olivier Certner
2023-04-17 17:48           ` Eli Zaretskii
2023-04-17 20:10             ` Olivier Certner
2023-04-19  0:54           ` Dmitry Gutov
2023-04-19  8:10             ` Olivier Certner
2023-04-20  8:55             ` Eli Zaretskii
2023-04-20  9:42               ` Olivier Certner
2023-04-20 10:22                 ` Dmitry Gutov
2023-04-17  8:04       ` Olivier Certner

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=83y1mtcx4g.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62693@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=ocert.dev@free.fr \
    /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).