unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Sacha Chua <sacha@sachachua.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-tangents@gnu.org
Subject: Re: A Zine/Newsletter for ELPA
Date: Sat, 15 Oct 2022 08:07:27 -0400	[thread overview]
Message-ID: <CAJGZZeJFcH07qEfDH5ruCOwgT0maXRw-2K9=hdFNj01nigQ2zw@mail.gmail.com> (raw)
In-Reply-To: <87zgdx5sqk.fsf@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 559 bytes --]

Hello, Philip, all!

On Sat, Oct 15, 2022, 05:41 Philip Kaludercic <philipk@posteo.net> wrote:

> That project is greater in scope, and would require more effort.  The
> idea I had was really just to highlight and promote ELPA packages.
> That being said, perhaps it wouldn't be out of place to mention changes
> and news from core Emacs development?
>

Sounds like fun. :) I don't have the time to do it myself (focusing on
EmacsConf at the moment), but if you want to start by writing package
highlights, I'd be happy to link to it in Emacs News.

Sacha

>

[-- Attachment #2: Type: text/html, Size: 1112 bytes --]

  reply	other threads:[~2022-10-15 12:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 21:13 A Zine/Newsletter for ELPA Philip Kaludercic
2022-10-15  7:10 ` Emanuel Berg
2022-10-15  9:41   ` Philip Kaludercic
2022-10-15 12:07     ` Sacha Chua [this message]
2022-10-15 15:24       ` John Yates
2022-10-15 16:00         ` Sacha Chua
2022-10-16 10:15           ` Philip Kaludercic
2022-10-16 12:32             ` Sacha Chua
2022-10-16 22:41               ` Emanuel Berg
2022-10-16 14:12             ` Eduardo Ochs
2022-10-16 14:31               ` Jean Louis
2022-10-16 22:37                 ` Emanuel Berg
2022-10-16 14:39               ` Philip Kaludercic
2022-10-15 20:42         ` Emanuel Berg
2022-10-15  7:14 ` Marcin Borkowski
2022-10-15  7:18   ` Emanuel Berg
2022-10-15  9:42 ` Lars Ingebrigtsen
2023-03-21 19:55 ` Philip Kaludercic
2023-03-22  2:42   ` orzodk
2023-03-22  8:55     ` Philip Kaludercic
2023-03-22 16:33       ` orzodk
2023-03-23 14:07         ` 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='CAJGZZeJFcH07qEfDH5ruCOwgT0maXRw-2K9=hdFNj01nigQ2zw@mail.gmail.com' \
    --to=sacha@sachachua.com \
    --cc=emacs-tangents@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.
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).