From: Joel Brobecker <brobecker@adacore.com>
To: "André Pönitz" <apoenitz@t-online.de>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Changing GDB's version numbering scheme
Date: Mon, 10 Sep 2018 17:32:00 -0000 [thread overview]
Message-ID: <20180910173243.GC3234@adacore.com> (raw)
In-Reply-To: <20180910171243.GB1832@klara.mpi.htwm.de>
> I am trying to imagine a situation where 36 lines of explanation of a
> numbering scheme helps people that *guess* wrong on any other numbering
> scheme
>
> And I fail.
I get what you are saying, but focusing on the length of the explanation
doesn't work in my opinion, because the "explanation" is actually
a detailed procedure for ourselves of what we will have to do in terms
of the new numbering scheme, which is an implementation detail.
What the GDB user will be seeing, on the other hand, is 2 or 3 releases
per major version, and those releases with the same major version are
made from the same branch, and therefore are fairly close in terms of
the code base.
--
Joel
next prev parent reply other threads:[~2018-09-10 17:32 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 [this message]
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
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=20180910173243.GC3234@adacore.com \
--to=brobecker@adacore.com \
--cc=apoenitz@t-online.de \
--cc=gdb-patches@sourceware.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