GNU bug report logs - #2678
vc-git-register not working when passed a directory argument

Previous Next

Package: emacs;

Reported by: Miles Bader <miles <at> gnu.org>

Date: Sun, 15 Mar 2009 06:15:04 UTC

Severity: normal

Done: Dan Nicolaescu <dann <at> ics.uci.edu>

Bug is archived. No further changes may be made.

Full log


Message #39 received at 2678 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: Miles Bader <miles <at> gnu.org>
Cc: 2678 <at> debbugs.gnu.org
Subject: Re: bug#2678: 23.0.91; vc-next-action in vc-dir acts strangely when  only adds are necessary
Date: Fri, 20 Mar 2009 21:30:32 -0700 (PDT)
Miles Bader <miles <at> gnu.org> writes:

  > On Sat, Mar 21, 2009 at 12:50 PM, Dan Nicolaescu <dann <at> ics.uci.edu> wrote:
  > >  > > It does, but there might be other things not working correctly with git,
  > >  > > try with hg and you will see it working correctly.
  > >  >
  > >  > It does what?
  > >
  > > vc-register creates a call to vc-start-logentry
  > > vc-start-logentry calls vc-finish-logentry which calls vc-resynch-buffer
  > > vc-resynch-buffer updates both the buffers that might have been
  > > affected by the VC command and the vc-dir display (this one via the
  > > vc-dir-resynch-file call).
  > 
  > Oh, incidentally -- that's another problem with the vc register stuff,
  > it prompts for a log message, which is useless for git (is it useful
  > for any non-cvs system?).  

Probably not...

  > Is there a way for the backend to suppress that behavior?

I've never seen this happen, so I don't know of the top of my head how
to avoid it.  Can you describe what you do so that I can reproduce it?




This bug report was last modified 15 years and 139 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.