unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sylvain Bougerel <sylvain.bougerel.devel@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 66985@debbugs.gnu.org
Subject: bug#66985: 29.1; Issue with `package.el` upgrading builtin (edge-case)
Date: Fri, 17 Nov 2023 17:37:59 +0800	[thread overview]
Message-ID: <CA+qKf8QiziO336m8hCuj_TM8+DMV_=0TEd2tTtXOzAMK-EVjaA@mail.gmail.com> (raw)
In-Reply-To: <87ttpm9n25.fsf@posteo.net>

On Thu, Nov 16, 2023 at 3:25 PM Philip Kaludercic <philipk@posteo.net> wrote:
> A short commit like this can be manually applied, and attributed to you,
> otherwise you should consult the CONTRIBUTING file in emacs.git for
> notes on how to format a patch and the commit message.

Thanks Philip, I'll read it for future reference. Feel free to make
the change as you see fit (as for attribution: this email chain is
enough)

> If you are really interested, you can take a look at bug#62720.

Thanks, I got the background now. I don't think it's necessary to go
further then.

>
> Nothing special, other than that I had been planning to re-write the
> function anyway, to make it simpler and re-usable by package-vc.

Let me know if you intend to maintain the same interface for
package-compute-transaction, in this case I can contribute a unit
test.





  reply	other threads:[~2023-11-17  9:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 13:11 bug#66985: 29.1; Issue with `package.el` upgrading builtin (edge-case) Sylvain Bougerel
2023-11-07 15:27 ` Sylvain Bougerel
2023-11-08  1:01   ` Sylvain Bougerel
2023-11-08  7:51 ` Philip Kaludercic
2023-11-08 16:30   ` Sylvain Bougerel
2023-11-10 17:05     ` Sylvain Bougerel
2023-11-15 13:06       ` Sylvain Bougerel
2023-11-15 13:30       ` Eli Zaretskii
2023-11-16  7:25       ` Philip Kaludercic
2023-11-17  9:37         ` Sylvain Bougerel [this message]
2023-11-27 17:18           ` Philip Kaludercic

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='CA+qKf8QiziO336m8hCuj_TM8+DMV_=0TEd2tTtXOzAMK-EVjaA@mail.gmail.com' \
    --to=sylvain.bougerel.devel@gmail.com \
    --cc=66985@debbugs.gnu.org \
    --cc=philipk@posteo.net \
    /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).