From: Lars Ingebrigtsen <larsi@gnus.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 20177@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#20177: 24.4: bookmark.el: show all annotations does not display in proper order (FIX INCLUDED)
Date: Wed, 26 Jun 2019 16:50:09 +0200 [thread overview]
Message-ID: <m3a7e4z9i6.fsf@gnus.org> (raw)
In-Reply-To: <m3k1d8z9nb.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 26 Jun 2019 16:47:04 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Boruch Baum <boruch_baum@gmx.com> writes:
>
>> On 2019-06-26 15:55, Lars Ingebrigtsen wrote:
>>> Boruch Baum <boruch_baum@gmx.com> writes:
>>>
>>> >> I think so too. Boruch, did you do any further work on this?
>>> >
>>> > No. ( ... year 2015 ... Thanks for the memories ... )
>>>
>>> In that case it seems unlikely that we'd be able to proceed with this
>>> bug report and I'm closing it. Please reopen if further progress can be
>>> made.
>>
>> I submitted two versions of patch, so if the objections are to the
>> 'fancy' one, which added features that aren't good enough,
>> why not accept the 'simple' patch that addresses the reported bug?
>
> Stefan did apply that one at the time...
(But he said "Thanks, attached" instead of "applied", which may explain
the confustion. :-))
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-06-26 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 10:21 bug#20177: 24.4: bookmark.el: show all annotations does not display in proper order (FIX INCLUDED) Boruch Baum
2015-03-26 1:56 ` Stefan Monnier
2019-06-25 17:35 ` Lars Ingebrigtsen
2019-06-25 19:43 ` Boruch Baum
2019-06-26 13:55 ` Lars Ingebrigtsen
2019-06-26 14:45 ` Boruch Baum
2019-06-26 14:47 ` Lars Ingebrigtsen
2019-06-26 14:50 ` Lars Ingebrigtsen [this message]
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=m3a7e4z9i6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=20177@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--cc=monnier@iro.umontreal.ca \
/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.