Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc] Versions and Branches
Date: Fri, 15 Mar 2002 08:41:00 -0000	[thread overview]
Message-ID: <3C922442.5020102@cygnus.com> (raw)
In-Reply-To: <2947-Fri15Mar2002105949+0200-eliz@is.elta.co.il>

> +@value{GDBN}'s release branch uses a slightly more complicated scheme.
>> +When the branch is first cut, the mainline version identifier is
>> +prefixed with the @var{major.minor} from of the previous release series
>> +but with @var{.90} appended.  As draft releases are drawn from the
>> +branch, the minor minor number (@var{.90}) is incremented.  Once the
>> +first release (@var{M.N}) has been made, the version prefix is updated
>> +to @var{M.N.0.90} (dot zero, dot ninety).  Follow on releases have an
>> +incremented minor minor version number (@var{.0}).
> 
> 
> Doesn't makeinfo whine about unlikely characters in @var or something?
> If it does, use @var{n}.@var{m} instead of @var{n.m} etc.

I didn't notice it.

So that I know I've got this straight:

	@var{.0} -> .0
	@var{M.N.0.90} -> @var{M}.@var{N}.0.90

BTW, are there any guidelines available online for this?

thanks!
Andrew

(I got the e.g.@: right on the second attempt)



  reply	other threads:[~2002-03-15 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 22:54 Andrew Cagney
2002-03-15  1:03 ` Eli Zaretskii
2002-03-15  8:41   ` Andrew Cagney [this message]
2002-03-15 10:54     ` Eli Zaretskii
2002-03-17  7:11       ` Andrew Cagney
2002-03-17 21:52         ` 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=3C922442.5020102@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@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