unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Niklas Eklund <niklas.eklund@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Name dtache.el
Date: Fri, 20 May 2022 15:19:13 +0000 (UTC)	[thread overview]
Message-ID: <7b7fb453-d2fa-4e72-a7f7-d6967813a291@posteo.net> (raw)
In-Reply-To: <jwvfsl42s8y.fsf-monnier+emacs@gnu.org>


May 20, 2022 16:32:05 Stefan Monnier <monnier@iro.umontreal.ca>:

> Niklas Eklund [2022-05-20 14:23:46] wrote:
>> I have gotten around to update the name of the package from dtache ->
>> detached.el.
>
> Is it really necessary?

I think it's desirable to make the switch, even though I dislike the 
annoyance it creates. I think its good to do the switch now then later 
on.

I have done commits renaming all the files and functions so updating the 
package archives is the last step.

>> I am not sure what to do about the name of the branch, if I was 
>> suppose
>> to update that or if a maintainer can do that to make it aligned with
>> the new name.
>
> Renaming requires some manual tweaking, yes.  I can take care of that.

Great

> But more importantly it's an annoyance for your users since updates
> won't be applied for them, so they may end up stuck at the old
> `dtache.el` release without realizing there's a new version under
> a different name.  We currently don't have any way to inform
> `package-update` and friends about a renaming :-(

Yes, that's unfortunate of course. Since I merged the renames of files 
and functions to the new names I thought that would indirectly inform 
users about the change.

Although those relying on releases won't get that information then. Maybe 
one solution to that is that I release a new version and only update the 
recipe ones it has become available on ELPA?

/Niklas



  reply	other threads:[~2022-05-20 15:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 16:35 Update URL to dtache.el package Niklas Eklund
2022-04-27 19:16 ` Tassilo Horn
2022-04-27 22:06 ` Stefan Monnier
2022-05-01 21:29   ` Niklas Eklund
2022-05-01 21:36     ` Niklas Eklund
2022-05-02  6:18       ` Stefan Monnier
2022-05-08 23:36         ` Name dtache.el Richard Stallman
2022-05-09 19:26           ` Niklas Eklund
2022-05-20 14:23             ` Niklas Eklund
2022-05-20 14:31               ` Stefan Monnier
2022-05-20 15:19                 ` Niklas Eklund [this message]
2022-05-20 15:25                   ` Stefan Monnier
2022-05-20 15:36                     ` Niklas Eklund
2022-05-20 16:33                       ` Niklas Eklund
2022-05-20 18:58                       ` Stefan Monnier
2022-05-20 19:27                         ` Niklas Eklund
2022-05-20 20:44                           ` Niklas Eklund
2022-05-20 21:00                             ` Stefan Monnier
2022-05-20 21:21                               ` Niklas Eklund
2022-05-20 21:35                                 ` Stefan Monnier
2022-05-21  7:38                                   ` Niklas Eklund
2022-05-21 14:44                                     ` Stefan Monnier
2022-05-21 16:13                                       ` Niklas Eklund
2022-05-20 15:50                 ` Eli Zaretskii

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=7b7fb453-d2fa-4e72-a7f7-d6967813a291@posteo.net \
    --to=niklas.eklund@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.org \
    /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).