From: Dan Nicolaescu <dann@ics.uci.edu>
To: Leo <sdl.web@gmail.com>
Cc: 5078@emacsbugs.donarmstrong.com
Subject: bug#5078: 23.1.50; vc broken
Date: Mon, 30 Nov 2009 11:59:56 -0800 (PST) [thread overview]
Message-ID: <200911301959.nAUJxuNO016161@godzilla.ics.uci.edu> (raw)
In-Reply-To: <m0ocmjde4d.fsf@cam.ac.uk> (Leo's message of "Mon, 30 Nov 2009 19:08:50 +0000")
Leo <sdl.web@gmail.com> writes:
> On 2009-11-30 16:46 +0000, Dan Nicolaescu wrote:
> > Leo <sdl.web@gmail.com> writes:
> >
> > > Please describe exactly what actions triggered the bug
> > > and the precise symptoms of the bug. If you can, give
> > > a recipe starting from `emacs -Q':
> > >
> > > For files that are placed in a subdirectory (where there's no .git) of a
> > > git repo, vc now thinks a file unchanged even if there are changes.
> >
> > Can you please send a detailed recipe starting from emacs -Q of how to
> > reproduce this?
>
> I think I am seeing an odd bug.
>
> There's a file in one of my projects that Emacs (with -Q) VC can't see
> its changes. However, I can use magit to see its changes without any
> problem. I tried to reproduce this problem with a newly created git repo
> but with no luck.
>
> Could you let me know how I can debug this further? Thanks.
With the file that you have problems with in the current buffer, try to debug:
M-: (vc-git-state (buffer-file-name)) RET
next prev parent reply other threads:[~2009-11-30 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m0tywaagjx.fsf@cam.ac.uk>
2009-11-30 11:44 ` bug#5078: 23.1.50; vc broken Leo
2009-11-30 16:46 ` Dan Nicolaescu
2009-11-30 19:08 ` Leo
2009-11-30 19:59 ` Dan Nicolaescu [this message]
2009-11-30 23:33 ` Leo
2009-12-01 0:07 ` Dan Nicolaescu
2009-12-01 1:18 ` Leo
2009-12-01 2:00 ` Dan Nicolaescu
2009-12-01 15:05 ` bug#5078: marked as done (23.1.50; vc broken) Emacs bug Tracking System
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=200911301959.nAUJxuNO016161@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=5078@emacsbugs.donarmstrong.com \
--cc=sdl.web@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.