Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com, Dave Korn <dk@artimi.com>
Subject: Re: dot five-o series versions - GDB 6.2.50
Date: Wed, 04 Aug 2004 16:56:00 -0000	[thread overview]
Message-ID: <20040804165457.GA17529@nevyn.them.org> (raw)
In-Reply-To: <411114D4.1000108@gnu.org>

On Wed, Aug 04, 2004 at 12:54:44PM -0400, Andrew Cagney wrote:
> >  Cut'n'paste error, or have I not understood the convention you were using
> >in that diagram?  Or both?
> >
> Mutter something rude, attempt #2.  thanks :-)
> 
> Hello,
> 
> Ref: http://www.iro.umontreal.ca/translation/HTML/maintainers.html
> 
> The translators are looking for a versioning schema that makes it easy 
> to undersand how two versions relate to each other.  Unfortunatly, GDB's 
> current versioning doesn't do this.  Without knowing the policy, it's 
> hard to know whats going on with:
> 
>     2004-09-03
>     6.2_2004-09_03
> 
> consequently, I'd like to propose that things be changed to the following:
> 
> M.N.5x:
> Indicate the mainline.  It's half way between releases -> .50.
> Ex 6.2.50, 6.2.50_2004-09-03
> 
> M.N.9x:
> Indicate pre release versions drawn from the branch.
> 
> M.N / M.N.O:
> The release.

This looks like a great idea to me.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-08-04 16:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 16:30 Andrew Cagney
2004-08-04 16:36 ` Dave Korn
2004-08-04 16:54   ` Andrew Cagney
2004-08-04 16:56     ` Daniel Jacobowitz [this message]
2004-08-11 17:38     ` Andrew Cagney
2004-08-04 17:05 ` Theodore A. Roth
2004-08-04 21:11   ` Steven Johnson
2004-08-04 21:27     ` Andrew Cagney
2004-08-04 23:16 jyates
2004-08-05 10:08 ` Andreas Schwab
2004-08-05 13:49 jyates
2004-08-05 15:41 ` Andrew Cagney

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=20040804165457.GA17529@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=dk@artimi.com \
    --cc=gdb@sources.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