On Wed, Oct 3, 2012 at 3:35 PM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
On 02/10/2012 21:14, Ryan Hill wrote:
Well, duh. You designed, developed, and are the sole architect of the
system.
Not by choice...
You made an error in the design. You might have had good reasons at
the
Nobody asked you to rollback months of work just because a few people
can't deal with the way you submit your logs.
Actually somebody did, suggesting I shouldn't file bugs until the log's
attached. And then proceeded to suggest that converting everything to
python and using pybugz is a cakewalk
On Wed, Oct 10, 2012 at 10:41 AM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
Sure. Preferences are great. Until said preferences mean that bugs that
_are_ 100% valid get closed, repeatedly, without being looked at.
I can't speak to the specifics of whatever the elephant in the room
is,
On Wed, Oct 10, 2012 at 3:41 PM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
Actually, that happened as well. Maybe you should actually review facts
before posting sure that you know that's going on. Just saying.
Ok
--
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
El dom, 07-10-2012 a las 08:55 +0200, Pacho Ramos escribió:
El dom, 07-10-2012 a las 12:08 +0800, Ben de Groot escribió:
On 7 October 2012 04:37, Chí-Thanh Christopher Nguyễn
chith...@gentoo.org wrote:
Pacho Ramos schrieb:
Hello
I am noticing for a long time that bugs related with
Pacho Ramos schrieb:
I am noticing for a long time that bugs related with ekiga,
opal, yate... are completely unattended by voip team for
years. If nobody from that team is willing to maintain
them, please move them to maintainer-needed to, at least,
reflect reality.
Any news here? I can
On Wed, Oct 10, 2012 at 5:53 PM, Chí-Thanh Christopher Nguyễn
chith...@gentoo.org wrote:
Pacho Ramos schrieb:
I am noticing for a long time that bugs related with ekiga,
opal, yate... are completely unattended by voip team for
years. If nobody from that team is willing to maintain
them,
On 10/6/2012 1:31 AM, Fabian Groffen wrote:
On 06-10-2012 00:47:57 -0700, Gregory M. Turner wrote:
In dev-lang/python*, we use
append-ldflags '-L.'
to ensure linking is performed against the built libpython.so in-tree,
rather than than in the one in $(libdir). But, this doesn't work if
On Wednesday 10 October 2012 18:47:46 Gregory M. Turner wrote:
+ if [[ ${CHOST} == *-cygwin* ]] ; then
+ fpeconfig=--without-fpectl
just re-use myconf. this is what it's for.
+ myconf=${myconf} ac_cv_func_bind_textdomain_codeset=yes
just export it:
export
On 10/9/2012 2:26 PM, Mike Frysinger wrote:
On Saturday 06 October 2012 03:47:57 Gregory M. Turner wrote:
My god, I am a horrible self-editor. Sorry. Please ignore the magnum
opus above and allow me to try again.
In dev-lang/python*, we use
append-ldflags '-L.'
to ensure linking is
On 10/10/2012 20:37, Gregory M. Turner wrote:
If the Makefiles are building against libraries expected to be in
${PWD}, it seems to me that the Makefiles should know to look there
automatically.
Using the -L . -lfoo is a very bad style in general. Just think what
happen if you're trying to
On Wednesday 10 October 2012 23:37:26 Gregory M. Turner wrote:
(1) is worse than (2), but it does have some quasi-legitimate usages.
For example, prefix bootstrap does this (or used to), as do many of the
crossdev-wrapper scripts. I've also resorted to such usage, myself,
when repairing a
12 matches
Mail list logo
