Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Tom Tromey <tom@tromey.com>, Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Changing GDB's version numbering scheme
Date: Wed, 07 Nov 2018 16:46:00 -0000	[thread overview]
Message-ID: <ce927dcd-f807-9fa8-f0aa-b2f1aa7bef73@FreeBSD.org> (raw)
In-Reply-To: <87o9b1rgei.fsf@tromey.com>

On 11/6/18 2:27 PM, Tom Tromey wrote:
>>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
> 
> Joel> Quick summary of the discussion so far: The only feedback this
> Joel> discussion drew was negative feedback. If you would like to support
> Joel> this proposal, you should speak up; otherwise, I'm inclined to
> Joel> let the matter drop.
> 
> I'm also in favor of it.  Historically I don't think the minor versions
> carried much meaning.  In the new scheme, I suppose the version still
> won't carry much meaning, but at least it won't pretend, and will be
> easy to explain.  Also, it is closer to what GCC does, which I think is
> a plus.

I also probably favor the new scheme for similar reasons to what Simon
articulated which is that there doesn't appear (to me) to be a clear
meaning of major version bumps (e.g. what qualifies gdb 6 vs 7 vs 8).
It seems gdb 7 -> 8 was maybe about switching from C to C++?  I haven't
been around the project long enough to be aware of other major bumps and
what they might have (or have not) signified, but it actually felt that
7.12 -> 8.0 was really about the same relative change as 7.11 -> 7.12 or
8.0 -> 8.1.  In the FreeBSD package we currently treat the major.minor
together as the "real" version number installing the binary as
/usr/local/bin/gdb{711,712,8,81,82} FWIW.

-- 
John Baldwin

                                                                            


      reply	other threads:[~2018-11-07 16:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10  8:49 Joel Brobecker
2018-09-10 12:24 ` Eli Zaretskii
2018-09-10 16:57   ` Simon Marchi
2018-09-10 17:08 ` André Pönitz
2018-09-10 17:32   ` Joel Brobecker
2018-10-31 17:25 ` Joel Brobecker
2018-11-01  9:31   ` Alan Hayward
2018-11-06 22:27   ` Tom Tromey
2018-11-07 16:46     ` John Baldwin [this message]

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=ce927dcd-f807-9fa8-f0aa-b2f1aa7bef73@FreeBSD.org \
    --to=jhb@freebsd.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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