unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Francesco Potortì" <pot@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 31460@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#31460: 25.2; vc-dired in SVN hides up-to-date files
Date: Mon, 06 Sep 2021 18:26:47 +0200	[thread overview]
Message-ID: <87lf49oek8.fsf@tucano.isti.cnr.it> (raw)
In-Reply-To: <87bl5b8kn3.fsf@gnus.org> (larsi@gnus.org)

>
>Francesco Potortì <pot@gnu.org> writes:
>
>>>>>> on an svn-controlled directory which is completely updated only
>>>>>> shows unregistered files.
>>>>>
>>>>> Or changed, deleted, etc.
>>>> 
>>>> Well, yes, by updated I mean that all changes have been committed.
>>>
>>>Committed when? And how?
>>
>> I edit a file under svn.  I save and I commit it with vc-next-action.
>> Then I look at the directory with vc-dir.
>
>(I'm going through old bug reports that unfortunately weren't resolved
>at the time.)
>
>This is how vc-dir is supposed to work -- it only shows files that
>aren't up-to-date (i.e., changed, unregistered, etc).  So this is
>working as designed, and I'm therefore closing this bug report.  (If I
>misunderstood what you meant here, please respond to the debbugs address
>and we'll reopen.)

I think you understood.  Only, at the time it seemd unreasonable to me
that vc-dir does not show all vc-controlled files.  In time, I got used
to it but I still think that being able to see all files is a must, and
it shluld be possible to use such a view by default.

Thanks for your maintainance work





      reply	other threads:[~2021-09-06 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 11:12 bug#31460: 25.2; vc-dired in SVN hides up-to-date files Francesco Potortì
2018-05-15 12:23 ` Dmitry Gutov
2018-05-15 12:49   ` Francesco Potortì
2018-05-17 12:16     ` Dmitry Gutov
2018-05-17 12:37       ` Francesco Potortì
2021-09-02  8:08         ` Lars Ingebrigtsen
2021-09-06 16:26           ` Francesco Potortì [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

  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=87lf49oek8.fsf@tucano.isti.cnr.it \
    --to=pot@gnu.org \
    --cc=31460@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=larsi@gnus.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).