unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: o0o0o耗子 <include_yy@qq.com>
Cc: 70526 <70526-done@debbugs.gnu.org>
Subject: bug#70526: 29.2; package-vc-upgrade failed with error message "File is not under version control"
Date: Sat, 27 Apr 2024 07:28:19 +0000	[thread overview]
Message-ID: <87frv7s1rg.fsf@posteo.net> (raw)
In-Reply-To: <tencent_35F37045C72C2B5CCA5568D7CE764E2CEF08@qq.com> ("o0o0o耗子 "'s message of "Wed, 24 Apr 2024 17:09:18 +0900")

"o0o0o耗子" <include_yy@qq.com> writes:

> &gt; As the buffer is hidden, I didn't see the need to clean it up.
> It can &gt; be re-used later on and might help with debugging. I think
> you are right. Now we fix this bug. Regards

I have pushed the changes, and will therefore close this bug report.
Thank you for your help!

-- 
	Philip Kaludercic on peregrine





      reply	other threads:[~2024-04-27  7:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23  1:51 bug#70526: 29.2; package-vc-upgrade failed with error message "File is not under version control" Yi Yue via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-23  8:31 ` Philip Kaludercic
2024-04-23 10:11 ` Yi Yue via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-23 19:35   ` Philip Kaludercic
2024-04-23 21:07     ` Yi Yue via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-24  2:00     ` Yi Yue via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-24  6:19       ` Philip Kaludercic
2024-04-24  7:02         ` Yi Yue via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-24  7:51           ` Philip Kaludercic
2024-04-24  8:09             ` o0o0o���� via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-27  7:28               ` Philip Kaludercic [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87frv7s1rg.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=70526-done@debbugs.gnu.org \
    --cc=include_yy@qq.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).