view BUGS @ 94805:89d37b54b964

* vc.el (vc-mark-resolved): Add `backend' argument. (vc-next-action): Pass it the backend. (vc-next-action, vc-checkout, vc-mark-resolved, vc-version-diff) (vc-merge, vc-rollback, vc-update, vc-transfer-file, vc-delete-file) (vc-default-comment-history, vc-default-create-snapshot) (vc-default-retrieve-snapshot, vc-default-revert, vc-annotate) (vc-annotate-revision-previous-to-line) (vc-annotate-show-diff-revision-at-line, vc-annotate-warp-revision): * vc-svn.el (vc-svn-checkout): * vc-mcvs.el (vc-mcvs-checkout): * vc-hooks.el (vc-state, vc-default-workfile-unchanged-p) (vc-working-revision, vc-before-save, vc-mode-line): Prefer vc-call-backend to vc-call so as not to recompute the backend.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Fri, 09 May 2008 16:41:26 +0000
parents 8ce686bd7f4f
children fb8bf24d2eb9
line wrap: on
line source

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"

Please first check the file etc/PROBLEMS (e.g. with C-h C-e in Emacs) to
make sure it isn't a known issue.