From: Eli Zaretskii <eliz@gnu.org>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] microMIPS support
Date: Thu, 17 May 2012 16:10:00 -0000 [thread overview]
Message-ID: <83obpmokik.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.1.10.1205171550550.11227@tp.orcam.me.uk>
> Date: Thu, 17 May 2012 16:06:37 +0100
> From: "Maciej W. Rozycki" <macro@codesourcery.com>
> CC: <gdb-patches@sourceware.org>
>
> > > if I place a @menu reference to that node in any of the upper sections.
> >
> > That's most probably because you added only some of the menus, not all
> > of them. The minor variation of your patch below doesn't have this
> > problem, it produces an Info manual without any warnings or errors.
>
> I added only some of the menus by your explicit request. You rejected my
> proposal that I made in response which added all of them and that was only
> trivially different to the version you have proposed now.
In that case, I apologize for my initial misunderstanding.
> > > I'll be pushing it in this form as soon as the MIPS16 manual
> > > function call change has been committed.
> >
> > I believe committing a patch over objections of the responsible
> > maintainer is against the rules described in MAINTAINERS (as I
> > understand them). So please don't do that.
>
> Certainly, next time I'll just drop any changes to the manual I disagree
> with.
I'd prefer that next time we could arrive at an agreement sooner.
> > Please use the slightly modified patch below instead.
>
> Thanks for your proposal, even though my original concern about pages
> containing single-entry menus still stands. This doesn't really matter
> however for two reasons, first and foremost because you have the power to
> override my objection to any changes to the manual, and second because it
> contains changes irrelevant to my change and as such I cannot integrate
> them. Please split changes to the existing pieces of the manual off and
> commit them separately. I'll extract the rest and fold into my change.
Which changes are irrelevant? I tried deliberately to put aside any
such unrelated changes, but maybe I missed some.
next prev parent reply other threads:[~2012-05-17 16:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 21:18 Maciej W. Rozycki
2012-04-25 6:20 ` Eli Zaretskii
2012-04-26 13:54 ` Maciej W. Rozycki
2012-04-26 14:14 ` Eli Zaretskii
2012-04-26 18:03 ` Maciej W. Rozycki
2012-04-26 20:39 ` Eli Zaretskii
2012-04-27 18:16 ` Maciej W. Rozycki
2012-04-27 18:24 ` Eli Zaretskii
[not found] ` <alpine.DEB.1.10.1204302334520.19835@tp.orcam.me.uk>
2012-05-02 16:39 ` Eli Zaretskii
2012-05-17 15:07 ` Maciej W. Rozycki
2012-05-17 16:10 ` Eli Zaretskii [this message]
2012-05-18 23:13 ` Maciej W. Rozycki
2012-05-19 8:20 ` Eli Zaretskii
2012-04-25 13:13 ` Yao Qi
2012-04-25 15:57 ` Maciej W. Rozycki
2012-04-25 15:54 ` Joel Brobecker
2012-04-25 17:18 ` Maciej W. Rozycki
2012-04-25 18:12 ` Joel Brobecker
2012-04-25 18:27 ` Maciej W. Rozycki
2012-04-26 18:38 ` Jan Kratochvil
2012-04-26 19:04 ` Maciej W. Rozycki
2012-04-26 19:29 ` Jan Kratochvil
2012-04-26 21:59 ` Maciej W. Rozycki
2012-04-27 7:11 ` Jan Kratochvil
2012-04-27 15:14 ` Maciej W. Rozycki
2012-04-27 15:29 ` Pedro Alves
2012-04-27 15:46 ` Maciej W. Rozycki
2012-04-27 15:54 ` Tom Tromey
2012-05-18 23:53 ` Maciej W. Rozycki
2012-05-18 21:32 ` [PATCH] microMIPS support (Linux signal trampolines) Maciej W. Rozycki
2012-05-18 22:25 ` Mark Kettenis
2012-05-21 14:33 ` Maciej W. Rozycki
2012-06-11 10:32 ` [PING][PATCH] " Maciej W. Rozycki
2014-09-28 11:12 ` [PATCH] " Maciej W. Rozycki
2014-10-06 0:46 ` [PING][PATCH] " Maciej W. Rozycki
2014-10-13 12:24 ` [PING^2][PATCH] " Maciej W. Rozycki
2014-10-20 17:01 ` [PING^3][PATCH] " Maciej W. Rozycki
2014-11-03 16:04 ` [PING^4][PATCH] " Maciej W. Rozycki
2014-11-16 8:58 ` [PATCH] " Joel Brobecker
2014-12-03 21:00 ` Maciej W. Rozycki
2012-05-18 23:47 ` [PATCH] microMIPS support Maciej W. Rozycki
2012-05-19 8:52 ` Eli Zaretskii
2012-05-22 0:07 ` Maciej W. Rozycki
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=83obpmokik.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@codesourcery.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