Re: No commit in vc?

[Dan Nicolaescu <dann@ics.uci.edu>]

Chong Yidong <cyd@stupidchicken.com> writes:

  > Juri Linkov <juri@jurta.org> writes:
  > 
  > >>>       (when pending-merge
  > >>>         (concat
  > >>>          (propertize "Warning            : " 'face 'font-lock-warning-face
  > >>>                      'help-echo shelve-help-echo)
  > >>>          (propertize "Pending merges, commit recommended before any other action"
  > >
  > > This warning is permanent and displayed even when there are no pending
  > > merges regardless whether the branch is lightweight or bound heavyweight.
  > > It seems .bzr/checkout/merge-hashes contains some old information from
  > > previous merges.
  > 
  > I am seeing this useless "warning" popping up every single time I use
  > VC-dir, on the bound heavyweight branch on which I work.
  > 
  > Unless there is a way to detect if a branch is bound and disable this
  > warning, I think the change should be reverted.

Sorry, I somehow missed Juri's message.   It seems that this is not
related to bound branches.  It looks like using the existence of
.bzr/checkout/merge-hashes to detect pending merges is not reliable.
I'll disable this as soon as I get a chance (if nobody beats me to it).

A better method to figure out the pending merge is needed, otherwise
this the header is just annoying.