From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: Merge of nickrob-async-20060513 to mainline?
Date: Wed, 30 Aug 2006 02:33:00 -0000 [thread overview]
Message-ID: <20060830023335.GA6377@nevyn.them.org> (raw)
In-Reply-To: <17652.63229.637451.185345@kahikatea.snap.net.nz>
On Wed, Aug 30, 2006 at 02:25:01PM +1200, Nick Roberts wrote:
>
> I have recently updated/merged the asynchronous branch (nickrob-async-20060513)
> that I am working on. The overall task is too great for me to complete alone
> and it has attracted no interest as a branch. For these reasons (and the
> coming release of Emacs 22) I would like to merge it with mainline GDB. I have
> tried to arrange that GDB on my branch will only build with the "--async"
> option for GNU/Linux on i386. This should mean that it should build and run as
> before on any other platform, and that itwill only run differently on
> i386-linux-gnu if the "--async" option is specified.
>
> If it passes the current testsuite and I add some new testcases for the
> asynchronous operation (probably in the MI part of the testsuite), may I make
> such a merge?
Could you remind me what this has to do with the release of emacs 22?
I'm not sure what interest you expected to generate on a branch, which
you didn't discuss on any of the mailing lists; as a rule, no one has
time to check out and poke at projects that no one tells them about.
The last time I heard status from you on the branch, it wasn't working.
I gather it's better off now. That makes it much more interesting.
I think that merging it in without review would be at the least unwise.
How big are the changes relative to mainline (diffstat)? Is there an
angle from which we can start looking at them?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-30 2:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 2:27 Nick Roberts
2006-08-30 2:33 ` Daniel Jacobowitz [this message]
2006-08-30 3:21 ` Nick Roberts
2006-08-30 4:01 ` Daniel Jacobowitz
2006-08-30 12:31 ` Eli Zaretskii
2006-08-30 21:34 ` Nick Roberts
2006-08-30 21:43 ` Daniel Jacobowitz
2006-08-30 23:45 ` Nick Roberts
2006-09-26 8:41 ` Nick Roberts
2006-09-26 12:38 ` Daniel Jacobowitz
2006-09-26 22:12 ` Nick Roberts
2006-09-26 22:24 ` Daniel Jacobowitz
2006-09-26 23:40 ` Nick Roberts
2006-09-29 1:50 ` Nick Roberts
2006-10-06 0:53 ` Nick Roberts
2006-10-06 1:26 ` Daniel Jacobowitz
2006-10-06 2:13 ` Nick Roberts
2006-10-06 3:24 ` Daniel Jacobowitz
2006-10-08 3:46 ` Nick Roberts
2006-10-09 18:00 ` async implies sync, was " Michael Snyder
2006-10-09 20:28 ` async implies sync Nick Roberts
2006-08-31 21:03 ` Merge of nickrob-async-20060513 to mainline? Mark Kettenis
2006-08-31 21:49 ` Nick Roberts
2006-08-31 22:29 ` Daniel Jacobowitz
2006-08-31 22:40 ` Nick Roberts
2006-08-31 22:53 ` Michael Snyder
2006-08-31 23:33 ` Nick Roberts
2006-08-31 23:37 ` Daniel Jacobowitz
2006-08-31 23:59 ` Jim Ingham
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=20060830023335.GA6377@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@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