From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Backtrace printing in batch mode ignores all customizations
Date: Sat, 25 Jan 2020 15:32:56 +0100 [thread overview]
Message-ID: <CAG7Bpapk2+Vx-QymFY=pc0Ti1VqMBcgT8zvQDLJTpcNqQY-87g@mail.gmail.com> (raw)
In-Reply-To: <jwvv9pfw4d3.fsf-monnier+emacs@gnu.org>
> > I don't have access to Emacs repository, so I cannot apply it myself.
>
> [ Anything we can do to help with that? ]
I wrote that as a reminder, because it sometimes looks like people
give approvement to my patches and then nothing happens, as if they
expect me to somehow apply them, which I have no way of doing.
This time it has been 10 days since the last email in this thread, but
I see no change in the source repository. Maybe the patch got
forgotten? Or if you wait for something additional from me, please say
so explicitly.
Paul
next prev parent reply other threads:[~2020-01-25 14:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 22:34 Backtrace printing in batch mode ignores all customizations Paul Pogonyshev
2019-12-21 9:22 ` Eli Zaretskii
2019-12-21 17:07 ` Paul Pogonyshev
2020-01-04 22:44 ` Stefan Monnier
2020-01-04 23:12 ` Paul Pogonyshev
2020-01-04 23:31 ` Stefan Monnier
2020-01-12 15:49 ` Paul Pogonyshev
2020-01-13 19:23 ` Stefan Monnier
2020-01-14 15:41 ` Eli Zaretskii
2020-01-14 17:51 ` Paul Pogonyshev
2020-01-14 19:57 ` Eli Zaretskii
2020-01-14 20:30 ` Stefan Monnier
2020-01-15 15:58 ` Eli Zaretskii
2020-01-15 17:34 ` Stefan Monnier
2020-01-15 17:54 ` Eli Zaretskii
2020-01-15 18:59 ` Stefan Monnier
2020-01-25 14:32 ` Paul Pogonyshev [this message]
2020-01-28 2:52 ` Richard Stallman
2020-01-27 3:55 ` Stefan Monnier
2020-01-29 11:09 ` Paul Pogonyshev
2020-01-31 14:14 ` Eli Zaretskii
2020-01-31 18:10 ` Paul Pogonyshev
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='CAG7Bpapk2+Vx-QymFY=pc0Ti1VqMBcgT8zvQDLJTpcNqQY-87g@mail.gmail.com' \
--to=pogonyshev@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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.