From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] PR mi/2077 "set edit off" breaks MI
Date: Mon, 20 Nov 2006 04:20:00 -0000 [thread overview]
Message-ID: <20061120042044.GA29293@nevyn.them.org> (raw)
In-Reply-To: <17761.5066.494599.865067@kahikatea.snap.net.nz>
On Mon, Nov 20, 2006 at 03:32:42PM +1300, Nick Roberts wrote:
> > > This patch is taken out of the async patch. It's probably a good idea to
> > > commit the different parts separately anyway.
> >
> > Definitely.
>
> I can split it into one async patch (the largest part) and several small MI
> patches. The MI patches are probably quite safe changes and the async part
> shouldn't interfere with normal use. Unless Elena becomes active again, I
> think it's likely that you will be the only person who would want to/be willing
> to review the latter. You have suggested that you would also like to use it
> for other reasons. When you have time to review it please tell me and I will
> re-submit it (without the MI changes).
We've branched; you have a patch ready; let's get it going! I'd be
glad to see this merged. I'm afraid I really haven't looked at what
you have so far; could you post a current patch that I can experiment
with?
I'll try to look at it during this week.
> I'll ask RMS, I've always been told that the committer's name should not be
> the one to go in the changelog.
True, but you've updated the patch and in general done more work on it;
the next best thing would probably be to either use Jim's name, or ask
him whose name to use.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-20 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 8:59 Nick Roberts
2006-11-17 21:35 ` Daniel Jacobowitz
2006-11-20 2:37 ` Nick Roberts
2006-11-20 4:20 ` Daniel Jacobowitz [this message]
2006-11-20 22:25 ` Nick Roberts
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=20061120042044.GA29293@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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