From: Stefan Kangas <stefankangas@gmail.com>
To: Robert Pluim <rpluim@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 66098@debbugs.gnu.org
Subject: bug#66098: Crash in itree.c on macOS with incomplete backtrace
Date: Sat, 23 Sep 2023 04:56:56 -0700 [thread overview]
Message-ID: <CADwFkmkoq-E4CiCAwu9bxdP4b-+4zrv73J8a7m23O9m-ojhLGQ@mail.gmail.com> (raw)
In-Reply-To: <87wmwis7dk.fsf@gmail.com>
Robert Pluim <rpluim@gmail.com> writes:
> Eli> Does "git reflog" help?
>
> This is why we have the numbered emacs builds in 'src/', no? Of
> course that wonʼt help if you clean before building.
My workflow is that I pull and rebuild many times a day, in the same
repository as I run the Emacs I use daily from. When I start or restart
Emacs, that version is just whatever happens to have been built last.
So I unfortunately don't think git reflog or numbered builds will help
with finding this information in my case.
next prev parent reply other threads:[~2023-09-23 11:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 8:47 bug#66098: Crash in itree.c on macOS with incomplete backtrace Stefan Kangas
2023-09-19 9:23 ` Robert Pluim
2023-09-19 10:09 ` Robert Pluim
2023-09-20 8:08 ` Paul Eggert
2023-09-20 8:22 ` Robert Pluim
2023-09-22 10:58 ` Stefan Kangas
2023-09-22 12:07 ` Robert Pluim
2023-09-23 13:02 ` Stefan Kangas
2023-09-25 8:36 ` Robert Pluim
2023-09-19 11:24 ` Eli Zaretskii
2023-09-22 10:51 ` Stefan Kangas
2023-09-22 12:36 ` Eli Zaretskii
2023-09-22 12:46 ` Robert Pluim
2023-09-23 11:56 ` Stefan Kangas [this message]
2023-09-23 12:42 ` Eli Zaretskii
2023-09-24 10:55 ` Stefan Kangas
2023-09-24 12:10 ` Eli Zaretskii
2023-09-24 12:25 ` Stefan Kangas
2023-09-24 21:01 ` Stefan Kangas
2023-09-25 3:38 ` Gerd Möllmann
2023-09-19 11:42 ` Gerd Möllmann
2023-09-19 12:21 ` Gerd Möllmann
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=CADwFkmkoq-E4CiCAwu9bxdP4b-+4zrv73J8a7m23O9m-ojhLGQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=66098@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rpluim@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 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.