From: Glenn Morris <rgm@gnu.org>
To: 7861@debbugs.gnu.org
Subject: bug#7861: svn vc dir does not show files with modified properties
Date: Tue, 25 Jan 2011 16:33:53 -0500 [thread overview]
Message-ID: <19775.16833.908621.995015@fencepost.gnu.org> (raw)
In-Reply-To: <tjtygw4rfe.fsf@fencepost.gnu.org>
Glenn Morris wrote (on Tue, 25 Jan 2011 at 16:14 -0500):
> This only affects ".", which vc-svn-after-dir-status explicitly skips
> for some reason.
Explicitly added 2009-04-15.
next prev parent reply other threads:[~2011-01-25 21:33 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 [this message]
2011-07-14 17:23 ` Lars Magne Ingebrigtsen
2022-02-07 0:17 ` bug#7861: vc-dir misses modified svn properties on "." Lars Ingebrigtsen
2022-03-07 2:48 ` 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=19775.16833.908621.995015@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=7861@debbugs.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).