From: Eli Zaretskii <eliz@gnu.org>
To: vincent.belaiche@gmail.com (Vincent Belaïche)
Cc: 28245@debbugs.gnu.org
Subject: bug#28245: 26.0.50; symbolic links not well handled by vc-dir
Date: Mon, 28 Aug 2017 20:44:01 +0300 [thread overview]
Message-ID: <838ti34mfy.fsf@gnu.org> (raw)
In-Reply-To: <84k21oybq2.fsf@AigleRoyal> (vincent.belaiche@gmail.com)
> From: vincent.belaiche@gmail.com (Vincent Belaïche)
> Cc: Vincent Belaïche <vincent.belaiche@gmail.com>
> Date: Sun, 27 Aug 2017 22:52:53 +0200
>
> > What does "svn status -v" show in that repository?
>
> When I do that, I see the original file `foo' only once. Please note
> that my bug report is erroneous. Actually, the symlink is
> trunk/test/foo, pointing as trunk/src/foo. trunk/src/foo is under change
> control, but the directory trunk/test and all its content is not under
> change control --- I have not yet imported it. So `svn status -v' done
> under trunk shows only, as far as trunk/test and its content are
> concerned, this:
>
> --8<----8<----8<----8<----8<-- begin -->8---->8---->8---->8---->8----
> ? test
> --8<----8<----8<----8<----8<-- end -->8---->8---->8---->8---->8----
Then maybe "svn status -v" is not the right (or not the only) command
you should try. My point is that you should find out which SVN
commands are invoked by vc-dir in this use case, and then see what did
SVN produce for these commands outside of Emacs.
It also could be that this is not a Windows-specific issue.
next prev parent reply other threads:[~2017-08-28 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 21:02 bug#28245: 26.0.50; symbolic links not well handled by vc-dir Vincent Belaïche
2017-08-27 14:21 ` Eli Zaretskii
2017-08-27 20:52 ` Vincent Belaïche
2017-08-28 17:44 ` Eli Zaretskii [this message]
2017-08-28 18:13 ` Glenn Morris
2017-08-28 18:19 ` Eli Zaretskii
2017-08-28 18:33 ` Glenn Morris
2017-08-28 18:38 ` Eli Zaretskii
2017-08-28 22:57 ` Vincent Belaïche
2017-08-28 1:04 ` Richard Stallman
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=838ti34mfy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28245@debbugs.gnu.org \
--cc=vincent.belaiche@gmail.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.