From: Felix <felix.dick@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rekado@elephly.net, emacs-devel@gnu.org
Subject: Re: [PATCH] [debbugs] Add mu4e support.
Date: Sat, 24 Dec 2022 16:45:37 +0100 [thread overview]
Message-ID: <87h6xk3ise.fsf@web.de> (raw)
In-Reply-To: <83zgbc4xdl.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Felix <felix.dick@web.de>
>> Cc: rekado@elephly.net, emacs-devel@gnu.org
>> Date: Sat, 24 Dec 2022 16:28:12 +0100
>>
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> From: Felix <felix.dick@web.de>
>> >> Cc: emacs-devel <emacs-devel@gnu.org>
>> >> Date: Sat, 24 Dec 2022 15:46:34 +0100
>> >>
>> >>
>> >> This Thread is now more than 5 years old.
>> >> Is there any plan for finishing this?
>> >> Or is this obsolete because of another way to use mu4e
>> >> for debbugs that i didn't find?
>> >
>> > Please state the bug number.
>>
>> I'm not shure if it ever was a reported bug.
>> I was searching for an option to use mu4e for debbugs,
>> that's how i found the Thread.
>> Or did i misunderstand you?
>
> Then please show the URL in the archives for the discussion thread. I
> couldn't find the thread, as you didn't even tell the date when it
> happened.
Sorry!
https://lists.gnu.org/archive/html/emacs-devel/2017-04/msg00662.html
next prev parent reply other threads:[~2022-12-24 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 14:46 [PATCH] [debbugs] Add mu4e support Felix
2022-12-24 15:04 ` Eli Zaretskii
2022-12-24 15:28 ` Felix
2022-12-24 15:47 ` Eli Zaretskii
2022-12-24 15:45 ` Felix [this message]
2022-12-24 16:26 ` Eli Zaretskii
2022-12-25 9:33 ` Michael Albinus
-- strict thread matches above, loose matches on Subject: below --
2017-04-23 10:05 Ricardo Wurmus
2017-04-23 17:53 ` Marcin Borkowski
2017-04-23 18:26 ` Michael Albinus
2017-04-28 13:22 ` Michael Albinus
2017-04-28 14:44 ` Stefan Monnier
2017-05-07 11:45 ` Ricardo Wurmus
2017-05-09 13:19 ` Michael Albinus
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=87h6xk3ise.fsf@web.de \
--to=felix.dick@web.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rekado@elephly.net \
/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.