GNU bug report logs - #63949
30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs

Previous Next

Full log

View this message in rfc822 format

From: Jens Schmidt <jschmidt4gnu <at> vodafonemail.de>
To: 63949 <at> debbugs.gnu.org
Subject: bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs
Date: Fri, 9 Jun 2023 00:44:39 +0200

[Message part 1 (text/plain, inline)]

Here come five patches for this issue, based on emacs-29:

0001-Always-erase-log-buffer-before-calling-vc-print-log.patch
0002-Always-erase-log-buffer-before-calling-vc-print-log.patch
0003-Always-erase-log-buffer-before-calling-vc-print-log.patch

  Name should be self-explaining, patches uncritical.

0004-Fix-documentation-bug-and-remove-obsolete-fixmes.patch

  `vc-deduce-fileset' uses `with-current-buffer' to protect the current
  buffer, which has not been reflected in comments.

0005-Avoid-setting-circular-vc-parent-buffer.patch

  This one fixes the issue related to VC parent buffer described in the
  previous update.  The "local" change seems to be logical (a buffer
  should not be the VC parent buffer of itself), but I'm not quite sure
  about any adverse "global" consequences.

[0001-Always-erase-log-buffer-before-calling-vc-print-log.patch (text/x-patch, attachment)]

[0002-Always-erase-log-buffer-before-calling-vc-print-log.patch (text/x-patch, attachment)]

[0003-Always-erase-log-buffer-before-calling-vc-print-log.patch (text/x-patch, attachment)]

[0004-Fix-documentation-bug-and-remove-obsolete-fixmes.patch (text/x-patch, attachment)]

[0005-Avoid-setting-circular-vc-parent-buffer.patch (text/x-patch, attachment)]

Previous Next

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