From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 14344-done@debbugs.gnu.org
Subject: bug#14344: 24.3.50; incorrect doc for `eval-defun-2'
Date: Mon, 6 May 2013 13:45:28 -0700 [thread overview]
Message-ID: <53DC12D5112C41D6A262A6C1C291B7FD@us.oracle.com> (raw)
In-Reply-To: <87txmfkgbb.fsf@mail.jurta.org>
> >> > The doc says, "With argument, insert value in current
> >> > buffer after the defun." What arg? There is no arg.
> >>
> >> Feel free to commit a fix, thank you,
> >
> > Someone who understands it can please feel free to commit a fix.
>
> I have no more understanding than you, but I committed your fix now
> because Kelly Dean in his report for bug#12985 asked to fix the
> same docstring. Please commit your fixes by yourself next time.
1. If you fixed the bug I reported, thank you.
2. However, I see nothing in the patch you included in the bug #12985 thread
that concerns this bug (#14344): nothing concerning the doc string of
`eval-defun-2'. Perhaps there was more to your fix than what is shown in the
#12985 bug thread (FWIW, bug #12985 is not merged with #14344).
3. I did NOT provide any fix for bug #14344 (or bug #12985), so what you say in
that regard makes no sense. You did not commit my fix. Presumably you
committed your fix.
3. I do not commit bug fixes. I sometimes file bugs that I come across, and I
sometimes provide suggested fixes for bugs that are reported.
4. AFAICT, in his report for bug #12985 Kelly Dean did NOT ask to fix the same
doc string. Bug #14344 is about the doc string of `eval-defun-2'. That
function and its doc string are not even mentioned in bug #12985.
next prev parent reply other threads:[~2013-05-06 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 15:40 bug#14344: 24.3.50; incorrect doc for `eval-defun-2' Drew Adams
2013-05-05 5:57 ` Stefan Monnier
2013-05-05 14:20 ` Drew Adams
2013-05-06 20:24 ` Juri Linkov
2013-05-06 20:45 ` Drew Adams [this message]
2013-05-06 20:50 ` Juri Linkov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53DC12D5112C41D6A262A6C1C291B7FD@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=14344-done@debbugs.gnu.org \
--cc=juri@jurta.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).