From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: GDB as a loader 3/3: --eval-command option
Date: Mon, 07 Nov 2005 20:46:00 -0000 [thread overview]
Message-ID: <uzmogdw4w.fsf@gnu.org> (raw)
In-Reply-To: <436F610C.5080508@st.com> (message from Andrew STUBBS on Mon, 07 Nov 2005 14:13:32 +0000)
> Date: Mon, 07 Nov 2005 14:13:32 +0000
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb@sources.redhat.com
>
> On looking at the NEWS files more closely I am a little uncertain what
> to do about the mainline file. The attached patch should do fine for the
> 6.4 branch however (I don't think this needs any more, does it?).
It's fine.
> The mainline does not contain anything about 6.4 yet. Presumably this
> will be merged across when the 6.4 stuff is completed?
Any patches that are committed to the branch and mainline, should be
mentioned in mainline's NEWS as well.
> Should I add a 6.5 section for my changes?
Only if we decide not to commit them to the branch as well.
Personally, I don't see why not have them in 6.4, they cannot possibly
harm anything.
next prev parent reply other threads:[~2005-11-07 20:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 11:33 Andrew STUBBS
2005-10-28 11:10 ` Andrew STUBBS
2005-10-28 13:04 ` Eli Zaretskii
2005-10-28 14:03 ` Andrew STUBBS
2005-10-28 17:05 ` Eli Zaretskii
2005-11-04 11:54 ` Andrew STUBBS
2005-11-05 2:51 ` Daniel Jacobowitz
2005-11-05 10:01 ` Eli Zaretskii
2005-11-07 14:01 ` Andrew STUBBS
2005-11-07 14:16 ` Andrew STUBBS
2005-11-07 17:27 ` Joel Brobecker
2005-11-07 18:06 ` Andrew STUBBS
2005-11-07 20:54 ` Eli Zaretskii
2005-11-07 20:46 ` Eli Zaretskii [this message]
2005-11-08 11:05 ` Andrew STUBBS
2005-11-13 17:38 ` Daniel Jacobowitz
2005-11-14 11:45 ` Andrew STUBBS
[not found] ` <20051114134816.GA21373@nevyn.them.org>
2005-11-14 15:57 ` Andrew STUBBS
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=uzmogdw4w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).