Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: eliz@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Updates to Ada sources, part 1 (longish)
Date: Sat, 05 Jun 2004 14:26:00 -0000	[thread overview]
Message-ID: <20040605142614.F25D04B104@berman.michael-chastain.com> (raw)

ac> I'm told Diego took rougly a day to prepare his tree-SSA ChangeLog entry.
eli> Who is Diego and how is the tree-SSA stuff relevant to our case?

Diego Novillo was in charge of the tree-ssa-20020619-branch of gcc.
This branch was active for about 23 months (starting at 20020619
and ending in May 2004).  After that much development on a branch,
Diego did a massive merge into gcc HEAD.

My recollection matches Andrew's, that Diego said he spent about one
full day day to prepare a ChangeLog entry for the merge.

Michael C


             reply	other threads:[~2004-06-05 14:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-05 14:26 Michael Elizabeth Chastain [this message]
2004-06-05 16:06 ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2004-06-03  5:12 Michael Elizabeth Chastain
2004-06-03  7:05 ` Paul Hilfinger
2004-06-04 11:45 ` Eli Zaretskii
2004-06-04 18:32   ` Andrew Cagney
2004-06-04 18:37     ` Joel Brobecker
2004-06-04 18:55       ` Daniel Jacobowitz
2004-06-04 19:10         ` Andrew Cagney
2004-06-05 10:11     ` Eli Zaretskii
2004-06-05 13:33       ` Andrew Cagney
2004-06-05 16:07         ` Eli Zaretskii
2004-06-05 23:15           ` Paul Hilfinger
2004-06-06  4:08             ` Eli Zaretskii
2004-06-07 13:40               ` Andrew Cagney
2004-06-02 10:03 Paul Hilfinger
2004-06-03  4:06 ` Eli Zaretskii
2004-06-03  4:16   ` Joel Brobecker
2004-06-03  4:30     ` Eli Zaretskii
2004-06-03  4:41       ` Joel Brobecker
2004-06-04 11:43         ` 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=20040605142614.F25D04B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=eliz@gnu.org \
    --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