From: Andrew Cagney <ac131313@redhat.com>
To: Nathanael Nerode <neroden@doctormoo.dyndns.org>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com, dj@redhat.com
Subject: Re: Top level: Separate src release scripts from Makefile (correct)
Date: Mon, 30 Sep 2002 08:24:00 -0000 [thread overview]
Message-ID: <3D986CBC.4090003@redhat.com> (raw)
In-Reply-To: <20020929222448.GA8342@doctormoo.dyndns.org>
> This time it actually works;
> 'make -f src-release gdb+dejagnu.tar' works (and the md5sum is there).
> 'make -f src-release gas.tar.bz' works.
>
> otherwise the same as
> http://gcc.gnu.org/ml/gcc-patches/2002-09/msg01761.html,
> including ChangeLog.
>
Today's GDB's snap appears to have worked. We've now got a stable baseline.
I've updated GDB's snapshot script so that it will work with either
src-release (prefered) or Makefile.in.
From GDB's point of view, I think the next steps are: commit the
src-release file; check that tomorrow's snap works; and finally, commit
the src/Makefile changes so all is back in sync.
Although, before all this you need a thumbs up from binutils.
Andrew
prev parent reply other threads:[~2002-09-30 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 15:29 Nathanael Nerode
2002-09-30 8:24 ` Andrew Cagney [this message]
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=3D986CBC.4090003@redhat.com \
--to=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@doctormoo.dyndns.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