[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called fro
From: |
Jens Schmidt |
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 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 |
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
Description: Text Data
0002-Always-erase-log-buffer-before-calling-vc-print-log.patch
Description: Text Data
0003-Always-erase-log-buffer-before-calling-vc-print-log.patch
Description: Text Data
0004-Fix-documentation-bug-and-remove-obsolete-fixmes.patch
Description: Text Data
0005-Avoid-setting-circular-vc-parent-buffer.patch
Description: Text Data
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, (continued)
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Jens Schmidt, 2023/06/18
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Dmitry Gutov, 2023/06/18
- Message not available
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Dmitry Gutov, 2023/06/19
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Jens Schmidt, 2023/06/21
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Dmitry Gutov, 2023/06/21
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Eli Zaretskii, 2023/06/21
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Dmitry Gutov, 2023/06/23
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Jens Schmidt, 2023/06/26
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Jens Schmidt, 2023/06/29
- bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Eli Zaretskii, 2023/06/30
bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs,
Jens Schmidt <=
bug#63949: 30.0.50; `vc-print-log´ does not erase buffer when called from *vc-change-log* buffer, at least for CVS logs, Jens Schmidt, 2023/06/08