From: Georg-Johann Lay <avr@gjlay.de>
To: Ian Lance Taylor <iant@google.com>
Cc: Vincent Legoll <vincent.legoll@gmail.com>,
gcc@gcc.gnu.org, overseers@gcc.gnu.org
Subject: Re: viewcvs: Python error
Date: Fri, 01 Jul 2011 18:59:00 -0000 [thread overview]
Message-ID: <4E0E18D8.1090307@gjlay.de> (raw)
In-Reply-To: <mcrliwr841p.fsf@coign.corp.google.com>
Ian Lance Taylor schrieb:
> Vincent Legoll writes:
>
>>This may be the changeset that broke pygments running on older
>>pythons (< 2.4):
>>
>>https://bitbucket.org/birkenfeld/pygments-main/changeset/8d3fbbf1ffdb
>
> Thanks for identifying the patch. I applied the reverse patch manually
> to gcc.gnu.org, and the problem appears to be fixed, at least for now.
>
> Ian
Hi, thanks for the fix, but it appears the revert changed bit too much.
This issue has returned:
http://gcc.gnu.org/ml/gcc/2011-04/msg00336.html
Johann
next prev parent reply other threads:[~2011-07-01 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTimu033Mmx21_chkdf78aQGyTFOoDg@mail.gmail.com>
2011-06-24 10:02 ` Georg-Johann Lay
2011-06-24 11:37 ` Vincent Legoll
2011-06-24 18:42 ` Ian Lance Taylor
2011-07-01 18:59 ` Georg-Johann Lay [this message]
2011-07-01 20:52 ` Ian Lance Taylor
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=4E0E18D8.1090307@gjlay.de \
--to=avr@gjlay.de \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=overseers@gcc.gnu.org \
--cc=vincent.legoll@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).