From: Christoph Junghans <ottxor@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Collecting items for EAPI 6
Date: Sat, 30 Mar 2013 12:39:14 -0600 [thread overview]
Message-ID: <CANgp9kyQunJgpJsb-3KkAed_uJkv=YCcp0w+B86Fz4r+MutZeQ@mail.gmail.com> (raw)
In-Reply-To: <20130328191559.39e66934@pomiocik.lan>
2013/3/28 Michał Górny <mgorny@gentoo.org>:
> Hello,
>
> As discussed with ulm, I'd like to start a thread for collecting
> initial items for EAPI 6. Preferably items which are either almost
> ready or are easy to implement and are non-controversial. In other
> words, thing which are practically ready to get on the actual list.
>
> As usual, each item should have a corresponding 'Future EAPI' bug which
> blocks the tracker [1].
>
> [1]:https://bugs.gentoo.org/show_bug.cgi?id=future-eapi
>
#444366 - unique subslot for live ebuilds
--
Christoph Junghans
http://dev.gentoo.org/~ottxor/
next prev parent reply other threads:[~2013-03-30 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 18:15 [gentoo-dev] Collecting items for EAPI 6 Michał Górny
2013-03-29 9:20 ` Tomáš Chvátal
2013-03-29 10:31 ` Pacho Ramos
2013-03-29 17:54 ` Andreas K. Huettel
2013-03-29 17:57 ` Ciaran McCreesh
2013-03-29 18:17 ` Andreas K. Huettel
2013-03-30 18:39 ` Christoph Junghans [this message]
2013-03-30 18:50 ` Ciaran McCreesh
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='CANgp9kyQunJgpJsb-3KkAed_uJkv=YCcp0w+B86Fz4r+MutZeQ@mail.gmail.com' \
--to=ottxor@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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