From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] MI Doco
Date: Fri, 30 Jun 2006 02:13:00 -0000 [thread overview]
Message-ID: <17572.34943.184715.155902@kahikatea.snap.net.nz> (raw)
In-Reply-To: <u3be652lr.fsf@gnu.org>
Eli Zaretskii writes:
> > From: Nick Roberts <nickrob@snap.net.nz>
> > Date: Thu, 15 Jun 2006 09:04:16 +1200
> > Cc: gdb-patches@sources.redhat.com
> >
> > > Of course I trust you; I just need to see the parts I didn't yet
> > > review.
> >
> > No, I mean as a tactic i.e trust my ability to DTRT, rather than my integrity.
>
> Well, if you mean approve unreviewed patches, I don't think I can do
> that. It's not about trust, it's about another pair of eyes going
> through the patch. Granted, documentation cannot break the program,
> but the procedure for approving patches is the same.
I mean trust me to only commit the parts that you have approved. Anyway...
> > Please remember though, the patch that I want to actually commit
> > will look quite different, because I also want to re-order the nodes.
>
> Reordering is a mechanical job that doesn't change any text, so
> there's no risk of introducing problems. Be sure to run makeinfo,
> though, before you commit.
...what's the status? The above reads like approval, but it's a bit too
subtle for me to confidently take it that way.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-06-30 2:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 0:23 Nick Roberts
2006-06-02 9:05 ` Eli Zaretskii
2006-06-02 10:23 ` Nick Roberts
2006-06-02 10:44 ` Eli Zaretskii
2006-06-03 23:57 ` Nick Roberts
2006-06-04 19:32 ` Eli Zaretskii
2006-06-09 19:07 ` Eli Zaretskii
2006-06-09 19:12 ` Daniel Jacobowitz
2006-06-09 19:52 ` Eli Zaretskii
2006-06-09 19:57 ` Daniel Jacobowitz
2006-06-10 7:32 ` Eli Zaretskii
2006-07-01 12:35 ` [commit] Fix MI prompt in manual (was: MI Doco) Eli Zaretskii
2006-06-09 19:58 ` [PATCH] MI Doco Bob Rossi
2006-06-09 23:27 ` Nick Roberts
2006-06-10 7:51 ` Eli Zaretskii
2006-06-10 21:40 ` Nick Roberts
2006-06-11 3:31 ` Eli Zaretskii
2006-06-11 10:47 ` Nick Roberts
2006-06-11 19:27 ` Eli Zaretskii
2006-06-11 21:42 ` Nick Roberts
2006-06-12 3:36 ` Eli Zaretskii
2006-06-12 6:19 ` Nick Roberts
2006-06-13 3:39 ` Eli Zaretskii
2006-06-13 4:46 ` Nick Roberts
2006-06-13 17:26 ` Eli Zaretskii
2006-06-13 21:15 ` Nick Roberts
2006-06-14 18:30 ` Eli Zaretskii
2006-06-14 21:05 ` Nick Roberts
2006-06-15 6:56 ` Eli Zaretskii
2006-06-30 2:13 ` Nick Roberts [this message]
2006-06-30 12:09 ` Eli Zaretskii
2006-06-30 14:12 ` Eli Zaretskii
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=17572.34943.184715.155902@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=eliz@gnu.org \
--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