From: Philip Kaludercic <philipk@posteo.net>
To: Sean Allred <allred.sean@gmail.com>
Cc: 67949-done@debbugs.gnu.org
Subject: bug#67949: 29.1; package-vc-{install,upgrade} modifies tracked files
Date: Fri, 29 Dec 2023 17:08:54 +0000 [thread overview]
Message-ID: <87jzox7x7d.fsf@posteo.net> (raw)
In-Reply-To: <m0sf3luiyg.fsf@epic96565.epic.com> (Sean Allred's message of "Fri, 29 Dec 2023 09:25:29 -0600")
Sean Allred <allred.sean@gmail.com> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>> Sean Allred <allred.sean@gmail.com> writes:
>>> Even after years of elisp work, I guess I just don't distribute new
>>> packages often enough to remember this :-)
>>>
>>> Seems this is discussed in Info node "(elisp) Library Headers".
>>
>> So what do you say, is this something where we should try and "do at
>> least something", or just refer to the Elisp manual and close this
>> report?
>
> Sorry, I could've been more explicit :-) This bug report can be closed.
> As you noted, it's intended behavior, and the correct way to do it is
> already discussed in the manual.
>
> The only improvement / follow-up I can see would be a note about
> `*-pkg.el` files being 'reserved', but I'll leave that to a normal patch
> submission.
>
> Thanks for your help :-)
OK, I'll close the bug report then. Thanks :)
> --
> Sean Allred
prev parent reply other threads:[~2023-12-29 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 6:52 bug#67949: 29.1; package-vc-{install,upgrade} modifies tracked files Sean Allred
2023-12-25 20:11 ` Philip Kaludercic
2023-12-28 21:16 ` Sean Allred
2023-12-29 14:34 ` Philip Kaludercic
2023-12-29 15:25 ` Sean Allred
2023-12-29 17:08 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzox7x7d.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=67949-done@debbugs.gnu.org \
--cc=allred.sean@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.