From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Doc: -var-delete
Date: Fri, 08 Dec 2006 17:29:00 -0000 [thread overview]
Message-ID: <u1wnauwi8.fsf@gnu.org> (raw)
In-Reply-To: <17780.35470.419020.947762@kahikatea.snap.net.nz> (message from Nick Roberts on Tue, 5 Dec 2006 09:52:30 +1300)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Tue, 5 Dec 2006 09:52:30 +1300
> Cc: gdb-patches@sources.redhat.com
>
> > > Why do you think it is not obvious?
> >
> > Because about the only kind of fix in the docs that is really obvious
> > is a typo or bad English.
>
> OK, sorry. I'll post to gdb-patches first, next time. To avoid any confusion,
> it might be a good idea to say this in MAINTAINERS.
Done; thanks for the suggestion.
next prev parent reply other threads:[~2006-12-08 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 3:57 Nick Roberts
2006-12-04 4:10 ` Eli Zaretskii
2006-12-04 4:45 ` Nick Roberts
2006-12-04 19:45 ` Eli Zaretskii
2006-12-04 20:57 ` Nick Roberts
2006-12-08 17:29 ` Eli Zaretskii [this message]
2006-12-08 17:32 ` [commit] Clarify obvious fix in the docs (was: Doc: -var-delete) Eli Zaretskii
2006-12-04 9:16 ` [commit] Doc: -var-delete Vladimir Prus
2006-12-04 10:29 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=u1wnauwi8.fsf@gnu.org \
--to=eliz@gnu.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