From: Eli Zaretskii <eliz@gnu.org>
To: Ben Longbons <brlongbons@gmail.com>
Cc: jan.kratochvil@redhat.com, gdb@sourceware.org
Subject: Re: [C++] System Requirements
Date: Mon, 16 Dec 2013 19:10:00 -0000 [thread overview]
Message-ID: <83wqj4d33e.fsf@gnu.org> (raw)
In-Reply-To: <CA+XNFZNM2x6Gz4NNZPSYUiqE1nm-cOb+aVtRWWiuhJais60oOg@mail.gmail.com>
> Date: Sun, 15 Dec 2013 09:04:09 -0800
> From: Ben Longbons <brlongbons@gmail.com>
> Cc: gdb@sourceware.org
>
> Personally, I don't get why people who are using long-term "stable"
> releases expect to be able to use the latest and greatest version of
> anything. If you only need to *use* gdb, you can just stick to older
> versions (including 7.7) which are still fully-featured releases.
Perhaps you never tried to use outdated versions of GDB too seriously
for too long. GDB constantly gets more and more useful features and
solves more and more bugs, so using an old version is a PITA. It's
not like GDB development aims only at supporting newer compiler
versions, you know. Just look at the commit logs, and you will see.
> But you're saying you're using RHEL5 for your *development* ? I'm not
> used to developers who can even stand not using the latest release.
Get used to that. Not every developer can determine for herself what
releases she will have installed. Life intervenes.
> Regardless of where we set the bounds, do you agree to the *concept*
> of having two different modes?
I don't. There's no reason to have that, and it certainly adds to the
overhead.
next prev parent reply other threads:[~2013-12-16 19:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 0:34 Ben Longbons
2013-12-14 0:40 ` Ben Longbons
2013-12-15 12:28 ` Michael Veksler
2013-12-17 2:29 ` Andrew Pinski
2013-12-17 4:02 ` Ben Longbons
2013-12-18 12:47 ` Michael Veksler
2013-12-18 19:16 ` Ben Longbons
2013-12-15 15:31 ` Jan Kratochvil
2013-12-15 17:04 ` Ben Longbons
2013-12-15 19:53 ` Mark Kettenis
2013-12-16 13:03 ` Ivo Raisr
2013-12-16 13:52 ` Phi Debian
2013-12-17 5:35 ` Sergio Durigan Junior
2013-12-16 19:10 ` Eli Zaretskii [this message]
2013-12-16 20:09 ` Ben Longbons
2013-12-16 19:05 ` Eli Zaretskii
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=83wqj4d33e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brlongbons@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.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