From: "Kevin Yu" <yujie052@gmail.com>
To: "Dan Nicolaescu" <dann@ics.uci.edu>
Cc: 996@emacsbugs.donarmstrong.com
Subject: bug#996: ntemacs 23.0.60; vc-dir bug
Date: Wed, 31 Dec 2008 13:17:37 +0800 [thread overview]
Message-ID: <42b562540812302117i5faf5360md887147755dcac1c@mail.gmail.com> (raw)
In-Reply-To: <200812301657.mBUGvtxi001256@mothra.ics.uci.edu>
Sorry, forgot to cc the emacs bug tracker.
1. Edit a file d:/myproject/src/myfile.c (emacs.exe -q myfile.c)
2. c-x v d select d:/myproject
* vc-dir * shows:
=================================
VC backend : SVN
Working dir: d:/myproject/
Repository : svn://127.0.0.1
./
src/
edited src\myfile.c
=================================
3. checkin myfile.c
* vc-dir * shows:
=================================
VC backend : SVN
Working dir: d:/myproject/
Repository : svn://127.0.0.1
./
src/
up-to-date src/myfile.c
edited src\myfile.c
=================================
On Wed, Dec 31, 2008 at 12:57 AM, Dan Nicolaescu <dann@ics.uci.edu> wrote:
> Kevin Yu <yujie052@gmail.com> writes:
>
> > Dan Nicolaescu <dann@ics.uci.edu> writes:
> > > What VC backend are you using here?
> > subversion
> >
> > I have tried on git. This bug doesn't exist.
> >
> > > Can you pleasedescribe the sequence of events starting from
> > >
> > > emacs -Q
> > >
> > > to get to that state?
> > 1. edit a file d:/myproject/src/myfile.c (myproject is the root
> > directory of this project. There must be a subdirectory in the path,
> > otherwise you can't reproduce this bug.(.../src/... here)
> >
> > 2. c-x v d select d:/myproject
>
> What is in the the *vc-dir* buffer at this point?
>
>
next prev parent reply other threads:[~2008-12-31 5:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 6:46 bug#996: ntemacs 23.0.60; vc-dir bug Kevin Yu
2008-12-28 18:18 ` Dan Nicolaescu
2008-12-30 12:17 ` Kevin Yu
2008-12-30 12:17 ` Kevin Yu
2008-12-30 16:57 ` Dan Nicolaescu
2008-12-31 5:17 ` Kevin Yu [this message]
2008-12-31 9:03 ` Dan Nicolaescu
2008-12-31 18:34 ` Stefan Monnier
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=42b562540812302117i5faf5360md887147755dcac1c@mail.gmail.com \
--to=yujie052@gmail.com \
--cc=996@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
/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.