From: Brian Dolbec <dolsen@gentoo.org>
To: "gentoo-catalyst@lists.gentoo.org" <gentoo-catalyst@lists.gentoo.org>
Subject: Re: [gentoo-catalyst] [PATCH 1/4] Initial rearrangement of the python directories
Date: Sat, 14 Dec 2013 04:12:04 -0800 [thread overview]
Message-ID: <1387023124.3897.148.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <CAEdQ38EAfPLAmhgca-h1-mhNaVujvo=w+rh8e9AJR1vAbaeBHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]
On Fri, 2013-12-13 at 21:22 -0800, Matt Turner wrote:
> On Fri, Dec 13, 2013 at 7:20 PM, Brian Dolbec <dolsen@gentoo.org> wrote:
> > New minimal start script, moving the original catalyst script to catalyst/main.py.
> > Add __init__.py's to modules and arch sub-pkgs.
> > Update the module loading paths for the new locations.
> > Fix catalyst_support import to new location and specify imported modules.
> > ---
> > arch/alpha.py | 75 --
> > arch/amd64.py | 83 --
> > arch/arm.py | 133 ---
> > arch/hppa.py | 40 -
> > arch/ia64.py | 16 -
> > arch/mips.py | 464 --------
> > arch/powerpc.py | 124 ---
> > arch/s390.py | 33 -
> > arch/sh.py | 116 --
> > arch/sparc.py | 42 -
> > arch/x86.py | 153 ---
>
> We're missing m68k.py. Looks like it was missed in rebase.
>
m68k was added much later in the rewrite. After the initial
restructuring. I guess this is yet another rebase error.
> > diff --git a/bin/catalyst b/bin/catalyst
> > new file mode 100755
> > index 0000000..a4e55db
> > --- /dev/null
> > +++ b/bin/catalyst
> > @@ -0,0 +1,46 @@
> > +#!/usr/bin/python -OO
> > +
> > +# Maintained in full by:
> > +# Catalyst Team <catalyst@gentoo.org>
> > +# Release Engineering Team <releng@gentoo.org>
> > +# Andrew Gaffney <agaffney@gentoo.org>
> > +# Chris Gianelloni <wolf31o2@wolf31o2.org>
> > +# $Id$
>
> Let's remove agaffney, wolf31o2 and the $Id$ tag.
>
> > +
> > +
> > +from __future__ import print_function
> > +
> > +import sys
> > +
> > +__maintainer__="Catalyst <catalyst@gentoo.org>"
> > +__version__="2.0.12.2"
>
> Wrong version.
>
yet another rebase error. This was done long ago before more bugfix
releases were done to master.
> Does catalyst still function immediately after this commit?
I doubt it. This is 1 of 4. I grouped these 4 together for that
reason.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2013-12-14 12:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 3:20 [gentoo-catalyst] rewrite-on-master patches, round-2 Brian Dolbec
2013-12-14 3:20 ` [gentoo-catalyst] [PATCH 1/4] Initial rearrangement of the python directories Brian Dolbec
2013-12-14 5:22 ` Matt Turner
2013-12-14 5:48 ` W. Trevor King
2013-12-14 12:12 ` Brian Dolbec [this message]
2013-12-14 14:17 ` Dylan Baker
2013-12-14 16:42 ` Brian Dolbec
2013-12-14 23:57 ` W. Trevor King
2013-12-14 3:20 ` [gentoo-catalyst] [PATCH 2/4] move catalyst_support, builder, catalyst_lock out of modules, into the catalyst's base namespace Brian Dolbec
2013-12-14 3:20 ` [gentoo-catalyst] [PATCH 3/4] rename the modules subpkg to targets, it better reflects what it contains Brian Dolbec
2013-12-14 3:20 ` [gentoo-catalyst] [PATCH 4/4] rename files directory to etc to better reflect the directories contents Brian Dolbec
2013-12-15 4:39 ` W. Trevor King
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=1387023124.3897.148.camel@big_daddy.dol-sen.ca \
--to=dolsen@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