From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH] update python requirements to 2.7
Date: Mon, 5 Oct 2015 23:52:15 -0700 [thread overview]
Message-ID: <20151005235215.6ee29d86.dolsen@gentoo.org> (raw)
In-Reply-To: <1444098969-12445-1-git-send-email-vapier@gentoo.org>
On Mon, 5 Oct 2015 22:36:09 -0400
Mike Frysinger <vapier@gentoo.org> wrote:
> We don't test older versions anywhere anymore as it's not in the tree.
> ---
> README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/README b/README
> index 0a0373c..46a99e8 100644
> --- a/README
> +++ b/README
> @@ -19,7 +19,7 @@ simple and reproducable manner. Use at your own
> risk. Requirements
> =======================
>
> -- Python 2.4 or greater (may still work with 2.3)
> +- Python 2.7 or greater (may still work with 2.6)
> - An ebuild repository snapshot (or an ebuild tree to create one)
> - A generic stage3 tarball for your architecture
> - shash for digest support
merge please.. one less thing to edit for the release :)
--
Brian Dolbec <dolsen>
prev parent reply other threads:[~2015-10-06 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 2:36 [gentoo-catalyst] [PATCH] update python requirements to 2.7 Mike Frysinger
2015-10-06 6:52 ` Brian Dolbec [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=20151005235215.6ee29d86.dolsen@gentoo.org \
--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