From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch;rfa:doc] 5.2.50 on mainline
Date: Wed, 22 Sep 2004 13:38:00 -0000 [thread overview]
Message-ID: <41517FD5.3080104@gnu.org> (raw)
In-Reply-To: <20040922005813.GG968@gnat.com>
> Just a small comment:
>
>
>>> ! <mainline>
>>> ! |
>>> ! 5.1.50_2002-03-03-cvs
>>> ! |
>>> ! +--------------------------.
>>> ! <branch> <mainline>
>>> ! | |
>>> ! 5.1.90 (draft #1) 5.2.50_2002-03-03-cvs
>>> ! | |
>>> ! 5.1.90_2002-03-03-cvs 5.2.50_2002-03-04-cvs
>>> ! | |
>>> ! 5.1.91 (draft #2) 5.2.50_2002-03-05-cvs
>>> ! | |
>>> ! 5.1.91_2002-03-05-cvs 5.2.50_2002-03-06-cvs
>>> ! | |
>>> ! 5.2 (release) 5.2.50_2002-03-06-cvs
>>> ! | |
>>> ! 5.2.0.90_2002-03-07-cvs 5.2.50_2002-03-07-cvs
>>> ! | |
>>> ! 5.2.1 (update) 5.2.50_2002-03-08-cvs
>>> ! |
>>> ! +----------- - -
>>> ! <branch>
>>> ! |
>>> ! 5.2.90 (draft #1)
>
>
> It seems more natural to me to have mainline be a straight line
> and then have each branch be cut out of mainline. Something like
> this:
The intent is to make the release heritage clear, hence 5.1.50, 5.1.90,
5.1.91, 5.2, 5.2.1 are all in a straight line. That clarity is what the
i18n group were asking for (but perhaphs not diagramatically :-).
Either way, I'll:
- strip out some of the mainline dates (no value add)
- add an <end-of-life> marker to the branch
- change <branch> to <gdb_5_2-branch> et.al.
Andrew
> <mainline>
> |
> 5.1.50_2002-03-03-cvs
> |
> +--------------------------.
> | <branch>
> | |
> 5.2.50_2002-03-03-cvs 5.1.90 (draft #1)
> | |
> 5.2.50_2002-03-04-cvs 5.1.90_2002-03-03-cvs
> | |
> 5.2.50_2002-03-05-cvs 5.1.91 (draft #2)
> | |
> 5.2.50_2002-03-06-cvs 5.1.91_2002-03-05-cvs
> | |
> 5.2.50_2002-03-06-cvs 5.2 (release)
> | |
> 5.2.50_2002-03-07-cvs 5.2.0.90_2002-03-07-cvs
> | |
> 5.2.50_2002-03-08-cvs 5.2.1 (update)
> |
> 5.2.50_2002-03-09-cvs
> |
> 5.2.50_2002-03-10-cvs
> |
> 5.2.50_2002-03-11-cvs
> |
> 5.2.50_2002-03-12-cvs
> |
> +--------------------------.
> | <branch>
> | |
> 5.3.50_2002-03-13-cvs 5.2.90 (draft #1)
> | |
>
>
> -- Joel
next prev parent reply other threads:[~2004-09-22 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 20:30 Andrew Cagney
2004-09-22 0:58 ` Joel Brobecker
2004-09-22 13:38 ` Andrew Cagney [this message]
2004-10-05 18:36 ` Andrew Cagney
2004-10-06 11:08 ` Eli Zaretskii
2004-10-06 22:20 ` Andrew Cagney
2004-10-08 9:47 ` Eli Zaretskii
2004-10-11 6:30 ` Andrew Cagney
2004-10-11 20:21 ` Eli Zaretskii
2004-10-12 19:15 ` 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=41517FD5.3080104@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--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