From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Re-organize the python structure
Date: Wed, 22 Jan 2014 10:49:44 -0500 [thread overview]
Message-ID: <52DFE898.1060205@gentoo.org> (raw)
In-Reply-To: <20140122051040.GN29063@odin.tremily.us>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/22/2014 12:10 AM, W. Trevor King wrote:
> On Sat, Jan 11, 2014 at 05:46:53PM -0800, Brian Dolbec wrote:
>> [PATCH 1/5] Initial rearrangement of the python directories
>> [PATCH 2/5] Move catalyst_support, builder, catalyst_lock out of...
>> [PATCH 3/5] Rename the modules subpkg to targets, to better reflect...
>> [PATCH 4/5] Move catalyst.conf and catalystrc to an etc/ directory
>> [PATCH 5/5] setup.py: Add disutils-based packaging
>
> Where do we stand on landing this? It's going to conflict with
> vapier's new arm64 patch [1].
>
> Cheers,
> Trevor
>
> [1]: http://article.gmane.org/gmane.linux.gentoo.catalyst/2640
>
Vapier's arm64 patch is trivial at best. We can rewrite it. If you want
to land some other conflicting change I can rewrite his patch after.
Keep with the rewrite, it is more important at this time.
Thanks,
Zero
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJS3+iYAAoJEKXdFCfdEflKPWYQALItr2bpIOIgeJhOWvc59mkI
M9HxI0Lgid7jGX7q9pHMGhIFG+qTvLyLghwV7snt6ZWKhoGgyoWM3FmHahudYpGh
YQaN3DhlMra+X6NMgai4Eskk8AtcyP7BMvNK/GI8GkyqomtPqLCdFQI5O8e9aC8w
uzKvKdAKTMbiT7L7qm5HgLAH0gOM5tWxQM51kaefEEAUSZlT6TmE2h/qC6Puwunz
FgL95bg1gxVBnQ6NR50Xj7v7z9qHvcBryLqJ6re2UYdPHlwVPrKPbJrMvLuuyrr3
NPlMLkoNybyw0N0NTWNaQU4PP5ytwychM6bdSQqUaujyNP0vKAvfpyBU4whJ8BB1
SWMNAz2tpq3cD2Jq6ClogSXn99Rw0HXF39Dw2lOnlSzHXP1pfvMpCP4yDAxbhBXO
MGGrvtPUm4QwVBvc4SlrPsob3aDIt24FSfdYIbdu8j8d22Y2b3d3M5BTHEDhDWyx
sVr11dXCZHFFsc1XjsTTX3sZg+i05CaE5amddS82h47lMCe56NQGxDLEJfZzsXSy
Md1a/b5FczeaggIKIol/R8xjqOHiT+2c7V6P1b+fPtfYAgjRYjeGQyMaU2xp9zUc
ApDwy/0mUtUTmwesBN2RsH2ZTeefbT/2WHXcaUFVICURGifQq7iSukeYR7zasjCm
PC21RpaUEWW79w4JEYb0
=4Kgx
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-01-22 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 1:46 [gentoo-catalyst] Re-organize the python structure Brian Dolbec
2014-01-12 1:46 ` [gentoo-catalyst] [PATCH 1/5] Initial rearrangement of the python directories Brian Dolbec
2014-01-12 20:25 ` Brian Dolbec
2014-02-22 17:10 ` W. Trevor King
2014-02-22 18:40 ` Brian Dolbec
2014-02-22 19:37 ` [gentoo-catalyst] [PATCH] Makefile: Fix PACKAGE_VERSION extraction W. Trevor King
2014-02-22 21:46 ` Brian Dolbec
2014-01-12 1:46 ` [gentoo-catalyst] [PATCH 2/5] Move catalyst_support, builder, catalyst_lock out of modules, into the catalyst namespace Brian Dolbec
2014-01-12 1:46 ` [gentoo-catalyst] [PATCH 3/5] Rename the modules subpkg to targets, to better reflect what it contains Brian Dolbec
2014-01-12 1:46 ` [gentoo-catalyst] [PATCH 4/5] Move catalyst.conf and catalystrc to an etc/ directory Brian Dolbec
2014-01-12 1:46 ` [gentoo-catalyst] [PATCH 5/5] setup.py: Add disutils-based packaging Brian Dolbec
2014-01-12 2:11 ` [gentoo-catalyst] " W. Trevor King
2014-01-12 3:36 ` Brian Dolbec
2014-01-22 5:10 ` [gentoo-catalyst] Re-organize the python structure W. Trevor King
2014-01-22 15:49 ` Rick "Zero_Chaos" Farina [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=52DFE898.1060205@gentoo.org \
--to=zerochaos@gentoo.org \
--cc=gentoo-catalyst@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