From: "Dave Korn" <dave.korn@artimi.com>
To: "'Joel Brobecker'" <brobecker@adacore.com>,
"'Andrew Cagney'" <cagney@redhat.com>
Cc: "'Nick Roberts'" <nickrob@snap.net.nz>, <gdb@sources.redhat.com>
Subject: RE: GDB version numbering
Date: Tue, 10 Jul 2007 19:42:00 -0000 [thread overview]
Message-ID: <00a501c7c32a$7011b580$2e08a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <20070710192534.GA3943@adacore.com>
On 10 July 2007 20:26, Joel Brobecker wrote:
>> The reason to bump the major version doesn't need to be technical and
>> previously hasn't. For instance, 5.x signified the freeing of GDB's CVS
>> repo. Here, similarly, we've got the GPLv3 change that while
>> non-technical is a very major change for GDB; something worth
>> considering as a trigger for a major version number bump:
>>
>> GDB 7 is GPLv3+
>> GDB 6 is GPLv2+
>
> Indeed. What do others think?
"Bikeshed".
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2007-07-10 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 10:19 Nick Roberts
2007-07-09 17:20 ` Joel Brobecker
2007-07-09 22:48 ` Nick Roberts
2007-07-10 16:58 ` Andrew Cagney
2007-07-10 19:23 ` Joel Brobecker
2007-07-10 19:33 ` Daniel Jacobowitz
2007-07-10 20:14 ` Eli Zaretskii
2007-07-10 19:42 ` Dave Korn [this message]
2007-07-10 20:17 ` 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='00a501c7c32a$7011b580$2e08a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=brobecker@adacore.com \
--cc=cagney@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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