From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Where and how should I announce a new port of emacs?
Date: Sat, 16 Apr 2016 23:02:31 +0200 [thread overview]
Message-ID: <87ega5qnbs.fsf@debian.uxu> (raw)
In-Reply-To: CAHsSLHD7aNV_N1p_8nuah2d_2iiJi5HOtjfE3LEk-ShZWqHoyw@mail.gmail.com
Pete Williamson <petewil@google.com> writes:
> 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.
What is a chromebook? A piece of hardware?
Anyway good job :)
I searched news.gwene.org, and there is no suitable
hit for "chrome" what I can see. There are some Linux
drivers but I suppose that isn't it. Or is it?
gmane.linux.drivers.unichrome.user (and -.devel)
gmane.linux.drivers.openchrome.user (ditto)
If it isn't, I suppose you could try
gmane.emacs.announce
but that group has only 59 posts...
But that is also going about it the wrong way!
If there is an up-and-coming
Chromebook-whatever-that-is-DIY-community then what
you should do is, take a break from the porting
hacking and get a mailing list up and running.
Then submit it to Gmane. And last, you don't have to
even ask where to post the news :)
--
underground experts united .... http://user.it.uu.se/~embe8573
Emacs Gnus Blogomatic ......... http://user.it.uu.se/~embe8573/blogomatic
- so far: 25 Blogomatic articles -
prev parent reply other threads:[~2016-04-16 21:02 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
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 [this message]
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=87ega5qnbs.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@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 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.