From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: dev-embedded@gentoo.org
Subject: Re: [gentoo-dev] dev-embedded/tigcc needs an urgent bump
Date: Sun, 29 Apr 2012 13:48:45 +0200 [thread overview]
Message-ID: <1335700125.18263.1.camel@belkin4> (raw)
In-Reply-To: <1335206106.8517.2.camel@belkin4>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
El lun, 23-04-2012 a las 20:35 +0200, Pacho Ramos escribió:
> Our stable versions are broken for a long time, they even don't compile,
> but we cannot stable latest testing version because of a buffer overflow
> problem. A bump could help, but looks like embedded team doesn't have
> enough time for it. Is anybody interested in taking care of it?
>
> Its bugs:
> https://bugs.gentoo.org/buglist.cgi?quicksearch=tigcc&list_id=978701
>
> Thanks
Or maybe we should simply treeclean it if nobody is willing to
fix/maintain it and since nothing in the tree needs it...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-04-29 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 18:35 [gentoo-dev] dev-embedded/tigcc needs an urgent bump Pacho Ramos
2012-04-29 11:48 ` Pacho Ramos [this message]
2012-04-29 19:50 ` Chris Reffett
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=1335700125.18263.1.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=dev-embedded@gentoo.org \
--cc=gentoo-dev@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