From: Jens Staal <staal1978@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] let's remove pkg(1)
Date: Fri, 22 May 2015 21:07:46 +0200 [thread overview]
Message-ID: <CAK8RtFpRbx7Hbyy=E4GBWec6OxCPzCEoyUR3PUU6GwaNqCH7VQ@mail.gmail.com> (raw)
In-Reply-To: <7271d099a8ed26d446bbd3a1ae40217d@u2.sfldmibb.det.wayport.net>
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
Den 22 maj 2015 21:01 skrev <sl@9front.org>:
>
> Proposal:
>
> As discussed on IRC, let's remove pkg(1). Any objections?
>
> For convenience, the pkg(1) source has been archived here:
>
> http://9front.org/extra/pkg.tgz
>
> sl
Sure. I am actually pretty excited about the new "ports". Hopefully this
will take off.
[-- Attachment #2: Type: text/html, Size: 556 bytes --]
next prev parent reply other threads:[~2015-05-22 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 17:01 sl
2015-05-22 19:07 ` Jens Staal [this message]
2015-05-22 19:10 ` [9front] " Kurt H Maier
2015-05-22 20:21 ` Iruatã Souza
2015-05-22 20:22 sl
2015-05-22 20:33 ` Iruatã Souza
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='CAK8RtFpRbx7Hbyy=E4GBWec6OxCPzCEoyUR3PUU6GwaNqCH7VQ@mail.gmail.com' \
--to=staal1978@gmail.com \
--cc=9front@9front.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.
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).