all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Pete Williamson <petewil@google.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Where and how should I announce a new port of emacs?
Date: Wed, 13 Apr 2016 22:50:53 +0200	[thread overview]
Message-ID: <877fg1cjwy.fsf@mbork.pl> (raw)
In-Reply-To: <CAHsSLHD7aNV_N1p_8nuah2d_2iiJi5HOtjfE3LEk-ShZWqHoyw@mail.gmail.com>


On 2016-04-13, at 20:19, Pete Williamson <petewil@google.com> wrote:

> I've got emacs working on a Chromebook at beta quality, and I'd like to
> inform emacs users on the  mailing list.
>
> What is the best way to go about this, and which list should I post to?
>  info-gnu-emacs seems like the right list, but I don't have permissions to
> post there.  emacs-devel does not seem like it will reach the right
> audience.
>
> More info on the port is available here:
> https://plus.google.com/u/0/118416397954909331171/posts/8dt2sM8YeeM
>
> I want to make sure I do the right thing and do things correctly.  The
> source code is available in the webports project, and I have started the
> process of porting changes back to the emacs source code base.

Just my 2 cents: making sure someone whose blog is aggregated on Planet
Emacsen writes about it seems also a good idea.

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



  reply	other threads:[~2016-04-13 20:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 20:19 Where and how should I announce a new port of emacs? Pete Williamson
2016-04-13 20:50 ` Marcin Borkowski [this message]
2016-04-16 21:06   ` Emanuel Berg
2016-04-14  6:23 ` Jude DaShiell
2016-04-16 21:03   ` Emanuel Berg
2016-04-17 18:55     ` Jude DaShiell
2016-04-20  0:54       ` Emanuel Berg
2016-04-16 21:02 ` Emanuel Berg

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=877fg1cjwy.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=help-gnu-emacs@gnu.org \
    --cc=petewil@google.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.