From: Andrew Cagney <cagney@gnu.org>
To: Ben Elliston <bje+dated+1087082990.8a63d3@air.net.au>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: top-level removal of dejagnu, expect
Date: Thu, 10 Jun 2004 14:08:00 -0000 [thread overview]
Message-ID: <40C86B52.1000304@gnu.org> (raw)
In-Reply-To: <20040610092946.A1602@mailhub.air.net.au>
>>This is going to percolate through the repository (modules file
>>> should also be adjusted eventually); you may want to hold off until
>>> Andrew has finished with GDB 6.1.1. Andrew, that should be soon,
>>> right?
(mumble something about going to do it yesterday ... :-)
> Isn't that being done off the gdb_6_1_branch?
Yes, but ...
> Anyway, I have no intention of touching the modules file.
... during the 6.1 release cycle people decided to play with the modules
file breaking the branch/release process. Hence the reasonable paranoia.
While this specific change won't technically affect the branch, I'd
still suggest doing the ``I'll wait a week before committing''. By then
GDB will be well clear.
enjoy,
Andrew
next prev parent reply other threads:[~2004-06-10 14:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 23:23 Ben Elliston
2004-06-09 23:26 ` Daniel Jacobowitz
2004-06-09 23:29 ` Ben Elliston
2004-06-10 14:08 ` Andrew Cagney [this message]
2004-06-10 20:10 ` Ben Elliston
2004-06-11 3:44 ` Andrew Cagney
2004-06-11 3:51 ` Ben Elliston
2004-06-11 4:15 ` Andrew Cagney
2004-06-11 4:18 ` Daniel Jacobowitz
2004-06-09 23:40 ` DJ Delorie
2004-06-10 0:15 ` Ben Elliston
2004-06-10 0:38 ` Christopher Faylor
2004-06-10 2:15 ` DJ Delorie
2004-06-10 2:19 ` Ben Elliston
2004-06-10 2:30 ` DJ Delorie
2004-06-10 2:34 ` Ben Elliston
2004-06-10 2:41 ` DJ Delorie
2004-06-10 2:50 ` Ben Elliston
2004-06-10 14:03 ` Andrew Cagney
2004-06-14 20:31 ` Alexandre Oliva
2004-06-10 2:22 ` Ian Lance Taylor
2004-06-10 2:27 ` Ben Elliston
2004-06-10 2:31 ` DJ Delorie
2004-06-14 20:25 ` Alexandre Oliva
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=40C86B52.1000304@gnu.org \
--to=cagney@gnu.org \
--cc=binutils@sources.redhat.com \
--cc=bje+dated+1087082990.8a63d3@air.net.au \
--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