all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Amin Bandali <bandali@gnu.org>
To: Nicolas Rybkin <nr68020@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: shorten-url
Date: Fri, 01 Mar 2019 22:30:58 -0500	[thread overview]
Message-ID: <87ef7qrlzh.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAJAcu-VR5H6chQSu=f=RcJYdsauVJR9kHF2tKsPrcYv59bB7+A@mail.gmail.com> (Nicolas Rybkin's message of "Fri, 1 Mar 2019 15:21:44 +0300")

Hello,

Your message(s) did reach the list:

- https://lists.gnu.org/r/emacs-devel/2019-02/msg00740.html
- https://lists.gnu.org/r/emacs-devel/2019-03/msg00006.html

It’s just that people haven’t had time/interest to look into and give
feedback etc.  As the message was sent very recently (~4 days ago), I’d
recommend giving it some time and trying again after a week or two, if
you don’t hear from anyone by then.

One thing I would mention is that if you’re interested in getting this
package into GNU ELPA if all goes well, you need fill out the copyright
assignment form if you haven’t already done so.  Unless of course you
had previously assigned the copyright for your contributions to Emacs,
in which case I believe filling a specific assignment for an individual
package may not be necessary.



  reply	other threads:[~2019-03-02  3:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 12:21 [ELPA] New package: shorten-url Nicolas Rybkin
2019-03-02  3:30 ` Amin Bandali [this message]
2019-03-02  3:34 ` Richard Stallman
2019-03-02 11:52   ` Nicolas Rybkin
2019-03-03  3:00     ` Richard Stallman
2019-03-03 14:36       ` Nicolas Rybkin
2019-03-04  3:27         ` Richard Stallman
2019-03-04  6:52           ` Nicolas Rybkin
2019-03-02 13:37   ` Yuri Khan
2019-03-02 16:05     ` Nicolas Rybkin
2019-03-02 17:37       ` Yuri Khan
2019-03-03  2:46         ` Van L
  -- strict thread matches above, loose matches on Subject: below --
2019-02-25 21:15 Bad Blue Bull

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=87ef7qrlzh.fsf@fencepost.gnu.org \
    --to=bandali@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=nr68020@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.