mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Kevyn-Alexandre Paré" <kapare@rogue-research.com>
To: musl@lists.openwall.com
Subject: Re: musl 1.0 release publicity
Date: Fri, 21 Mar 2014 09:38:01 -0400	[thread overview]
Message-ID: <CACgAsMdDNw81GaHFPdKY6UQ4fPzkU=F3xXjLVH9se7Ko3TCxZg@mail.gmail.com> (raw)
In-Reply-To: <20140320095615.GA28295@brightrain.aerifal.cx>

Great job!

I have created a bugzilla to add it in Yocto...

https://bugzilla.yoctoproject.org/show_bug.cgi?id=6024

- KA

On Thu, Mar 20, 2014 at 5:56 AM, Rich Felker <dalias@aerifal.cx> wrote:
> Hi everyone,
>
> With the release of 1.0, now is the time to publicize musl!
> Here are some
>
> - Tweet about the release and/or retweet posts by me (@RichFelker) and
>   musl (@musllibc) using the #musl and #libc hashtags. Feel free to
>   mention your own projects using musl too at the same time.
>
> - Upvote our story submission to slashdot:
>   http://slashdot.org/submission/3422139/musl-libc-hits-10-milestone
>
> - Upvote the link on Hacker News:
>   https://news.ycombinator.com/item?id=7434554
>
> - Notify other news sites of the release (you can use the blurb from
>   the slashdot submission or say something in your own words). I'm
>   already sending to the ones I can think of but hearing from multiple
>   people shouldn't hurt.
>
> - If you have a project using musl, go ahead and ride the publicity to
>   submit stories about your own project too.
>
> - If you have patches for other projects to make them build/work
>   correctly on musl, please _politely_ submit them upstream.
>
> I'm sure there are some things I'm overlooking, but these are a good
> start.
>
> Rich


      parent reply	other threads:[~2014-03-21 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20  9:56 Rich Felker
2014-03-20 19:49 ` Solar Designer
2014-03-21  2:51   ` Christopher Meng
2014-03-21 14:03     ` Emmanuel DELOGET
2014-03-21 13:38 ` Kevyn-Alexandre Paré [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='CACgAsMdDNw81GaHFPdKY6UQ4fPzkU=F3xXjLVH9se7Ko3TCxZg@mail.gmail.com' \
    --to=kapare@rogue-research.com \
    --cc=musl@lists.openwall.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 public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).