From: Eli Zaretskii <eliz@gnu.org>
To: Vasilij Schneidermann <v.schneidermann@gmail.com>
Cc: 22114@debbugs.gnu.org
Subject: bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stopping
Date: Tue, 08 Dec 2015 19:38:30 +0200 [thread overview]
Message-ID: <834mfsdend.fsf@gnu.org> (raw)
In-Reply-To: <20151208164049.GB1080@odonien.bevuta.com>
> Date: Tue, 8 Dec 2015 17:40:49 +0100
> From: Vasilij Schneidermann <v.schneidermann@gmail.com>
> Cc: 22114@debbugs.gnu.org
>
> Or imposing a restriction on the profiler workflow such as that it must
> be running to produce a profiler report...
Sorry, I don't understand this comment. If the report can be produced
when the profiler is stopped, then the limitation is lifted, right?
next prev parent reply other threads:[~2015-12-08 17:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 8:13 bug#22114: 24.5; [PATCH] Allow profiler.el to display reports after stopping Vasilij Schneidermann
2015-12-08 16:22 ` Eli Zaretskii
2015-12-08 16:32 ` Vasilij Schneidermann
2015-12-08 17:28 ` Eli Zaretskii
2015-12-08 17:42 ` John Wiegley
2015-12-08 17:56 ` Vasilij Schneidermann
2015-12-08 18:02 ` John Wiegley
2015-12-08 18:12 ` Vasilij Schneidermann
2015-12-08 18:08 ` Eli Zaretskii
2015-12-08 18:14 ` John Wiegley
2015-12-10 9:18 ` Vasilij Schneidermann
2015-12-13 20:33 ` Vasilij Schneidermann
2015-12-13 22:18 ` Vasilij Schneidermann
2015-12-14 4:21 ` Stefan Monnier
2015-12-14 8:28 ` Vasilij Schneidermann
2015-12-14 14:43 ` Stefan Monnier
2015-12-14 18:23 ` Vasilij Schneidermann
2015-12-15 4:29 ` Stefan Monnier
2019-06-27 18:18 ` Lars Ingebrigtsen
2019-06-30 9:21 ` Vasilij Schneidermann
2019-06-30 12:34 ` Basil L. Contovounesios
2015-12-08 16:40 ` Vasilij Schneidermann
2015-12-08 17:38 ` Eli Zaretskii [this message]
2015-12-08 17:44 ` Vasilij Schneidermann
2015-12-08 18:10 ` Eli Zaretskii
2015-12-08 19:15 ` Vasilij Schneidermann
2015-12-08 19:21 ` John Wiegley
2015-12-08 20:12 ` Eli Zaretskii
2015-12-08 20:39 ` John Wiegley
2015-12-08 20:10 ` Eli Zaretskii
2019-06-25 14:46 ` Lars Ingebrigtsen
2019-06-27 14:09 ` 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
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=834mfsdend.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22114@debbugs.gnu.org \
--cc=v.schneidermann@gmail.com \
/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).