unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Dan Nicolaescu <dann@ics.uci.edu>, 7861@debbugs.gnu.org
Subject: bug#7861: vc-dir misses modified svn properties on "."
Date: Mon, 07 Feb 2022 01:17:25 +0100	[thread overview]
Message-ID: <877da734yy.fsf_-_@gnus.org> (raw)
In-Reply-To: <m3k4bku67n.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 14 Jul 2011 19:23:24 +0200")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

>>> This only affects ".", which vc-svn-after-dir-status explicitly skips
>>> for some reason.
>>
>> Explicitly added 2009-04-15.
>
> So...  is this a bug or a feature?  :-)

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

This was added by:

commit 524a655d93e4e535ccab96f6650a18f8d1816e03
Author:     Dan Nicolaescu <dann@ics.uci.edu>
AuthorDate: Wed Apr 15 00:32:47 2009 +0000

    (vc-svn-after-dir-status): Fix regexp to allow for
    file names with leading spaces.  Ignore "." if it appears as a
    filename.

But the commit message doesn't say anything about why "." should be
ignored.  Dan, do you remember?  It's only been 13 years, after all.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-02-07  0:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 21:33 bug#7861: svn vc dir does not show files with modified properties Sam Steingold
2011-01-19  3:49 ` Glenn Morris
2011-01-25 16:57   ` Sam Steingold
2011-01-25 18:37     ` Glenn Morris
2011-01-25 21:14       ` Glenn Morris
2011-01-25 21:33         ` Glenn Morris
2011-07-14 17:23           ` Lars Magne Ingebrigtsen
2022-02-07  0:17             ` Lars Ingebrigtsen [this message]
2022-03-07  2:48               ` bug#7861: vc-dir misses modified svn properties on "." Lars Ingebrigtsen

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=877da734yy.fsf_-_@gnus.org \
    --to=larsi@gnus.org \
    --cc=7861@debbugs.gnu.org \
    --cc=dann@ics.uci.edu \
    --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 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).