From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH 1/4] catalyst: Specify python2 rather than the generic python
Date: Fri, 11 Oct 2013 14:11:40 -0700 [thread overview]
Message-ID: <1381525900.24205.87.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <CAEdQ38GuQ0-j=QU7LkZo_y8d=UUvnwZAmSbgawGuL1277NjxTA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
On Fri, 2013-10-11 at 12:28 -0700, Matt Turner wrote:
> On Fri, Oct 11, 2013 at 11:15 AM, Brian Dolbec <dolsen@gentoo.org> wrote:
> > This is only
> > good for running the code directly from the git checkout.
>
> actually seems useful. We've had clearly broken commits go upstream,
> and if the author had been able to test from a git checkout we
> probably could have avoided that.
Which is why I made the rewrite code able to run from the checkout fully
and properly. Just cd into the directory, run "source ./testpath" and
it's will run completely from the checkout.
> What I mean is that I don't want to turn down contributions from new
> developers because there's a big backlog of work that hasn't gone
> upstream.
>
I don't want to discourage others either. It is just much better to
encourage some help on the rewrite in my opinion. Especially since
patches 2 & 3 have already been done in the rewrite branch. Some of
patch 4 might have been done already, but likely not all. If the
rewrite is to take over from the master branch...
The rewrite is not far from being able to take over as master. There
are a few rebase errors in the rewrite-on-master you did. There is some
cleanup work to do on the autoresume operation. Then a little more
testing with the tree defaults relocated to ensure I haven't missed any
hard coding.
The default tree location move is waiting on the catalyst rewrite code
to go live producing stages, etc..
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2013-10-11 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 17:38 [gentoo-catalyst] [PATCH 1/4] catalyst: Specify python2 rather than the generic python Dylan Baker
2013-10-11 17:38 ` [gentoo-catalyst] [PATCH 2/4] Catalyst: use a more pythonic method to import modules Dylan Baker
2013-10-11 18:00 ` [gentoo-catalyst] " Dylan Baker
2013-10-11 17:38 ` [gentoo-catalyst] [PATCH 3/4] catalyst: split combined import Dylan Baker
2013-10-11 17:38 ` [gentoo-catalyst] [PATCH 4/4] catalyst: Remove commented sections of code Dylan Baker
2013-10-11 18:15 ` [gentoo-catalyst] [PATCH 1/4] catalyst: Specify python2 rather than the generic python Brian Dolbec
2013-10-11 19:28 ` Matt Turner
2013-10-11 21:11 ` Brian Dolbec [this message]
2013-10-11 21:58 ` Matt Turner
2013-10-13 9:19 ` Dylan Baker
2013-10-13 16:33 ` Brian Dolbec
2013-10-13 20:52 ` Dylan Baker
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=1381525900.24205.87.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