From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: fgunbin@fastmail.fm, emacs-devel@gnu.org
Subject: RE: [imenu.el] Attempt to fix broken imenu--generic-function
Date: Wed, 18 Jul 2018 04:36:44 +0000 (UTC) [thread overview]
Message-ID: <c721c9a0-ba48-41cb-aba2-ce4130fa8d01@default> (raw)
In-Reply-To: <<83a7qp6zg5.fsf@gnu.org>>
> > > > > your commit
> > > > > 77166e0da2d58f2f6436989b7059d913be5b3439
> > > >
> > > > Sorry, but I have no idea what you're talking
> > > > about. I haven't committed anything. Is this
> > > > about some Emacs bug? If so, what bug #?
> > >
> > > commit hash
> > > (77166e0da2d58f2f6436989b7059d913be5b3439).
> >
> > [searches mail messages...] I didn't commit
> > it, but yes, it's for bug #32024. (Shouldn't
> > the commit log say that?)
>
> It does, doesn't it? [shows bug # in log entry]
That was my question. Good.
I'm reading this in emacs-devel. Nothing was
said here about the bug. Only a hex commit
number was presented, saying it was my commit.
I know nothing about that. I didn't commit the
patch. (But thank you for committing it.)
> commit 77166e0da2d58f2f6436989b7059d913be5b3439
Since the commit log does mention the bug, the
bug # could have been cited here. Or the log
entry could have been shown here, as you've
done now.
Anyway, mystery, and problem, solved - thanks
to all.
next prev parent reply other threads:[~2018-07-18 4:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 20:34 [imenu.el] Attempt to fix broken imenu--generic-function Filipp Gunbin
2018-07-17 20:55 ` Drew Adams
2018-07-17 22:14 ` Filipp Gunbin
2018-07-17 23:18 ` Drew Adams
2018-07-18 2:38 ` Eli Zaretskii
2018-07-18 13:12 ` Filipp Gunbin
[not found] ` <<03bf24b4-7040-451d-9a98-e02315b33f91@default>
[not found] ` <<83a7qp6zg5.fsf@gnu.org>
2018-07-18 4:36 ` Drew Adams [this message]
2018-07-18 5:01 ` 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=c721c9a0-ba48-41cb-aba2-ce4130fa8d01@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fgunbin@fastmail.fm \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.