From: Andreas Schwab <schwab@linux-m68k.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Tor Kringeland <tor.kringeland@ntnu.no>,
"Emacs-devel@gnu.org" <Emacs-devel@gnu.org>
Subject: Re: More build times
Date: Sat, 25 Jun 2022 17:15:10 +0200 [thread overview]
Message-ID: <87mte0g4g1.fsf@igel.home> (raw)
In-Reply-To: <87ilooiz4n.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 25 Jun 2022 16:41:44 +0200")
On Jun 25 2022, Lars Ingebrigtsen wrote:
> larsi@ns3206854:/mnt/ram/bench$ git rev-list -n 1 --before="Fri Jun 17 00:00:00 2022 +0200" HEAD
> f419de6eca4ca6a6d03db1eec4b9086a3d1e5b86
>
> Which gives me the commit that didn't exist in master at that point.
But it is reachable from master. That's what you have asked for.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-06-25 15:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 12:17 More build times Lars Ingebrigtsen
2022-06-25 13:44 ` Lars Ingebrigtsen
2022-06-25 13:51 ` Tor Kringeland
2022-06-25 14:41 ` Lars Ingebrigtsen
2022-06-25 15:15 ` Andreas Schwab [this message]
2022-06-25 14:16 ` Eli Zaretskii
2022-06-25 14:44 ` Lars Ingebrigtsen
2022-06-25 15:16 ` Eli Zaretskii
2022-06-25 15:30 ` Lars Ingebrigtsen
2022-06-29 16:22 ` Gregory Heytings
2022-06-30 8:12 ` Lars Ingebrigtsen
2022-06-30 8:30 ` Gregory Heytings
2022-06-30 8:47 ` Stephen Berman
2022-06-30 8:49 ` Lars Ingebrigtsen
2022-06-30 8:42 ` Andreas Schwab
2022-06-30 8:55 ` Stephen Berman
2022-06-30 16:07 ` Juri Linkov
2022-06-30 16:31 ` Andreas Schwab
2022-06-30 17:10 ` Juri Linkov
2022-06-30 13:27 ` Mattias Engdegård
2022-06-30 17:50 ` Gregory Heytings
2022-06-30 17:53 ` Gregory Heytings
2022-06-25 14:34 ` Yuri Khan
2022-06-25 14:49 ` Lars Ingebrigtsen
2022-06-26 8:30 ` Stefan Monnier
2022-06-26 15:38 ` Lars Ingebrigtsen
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=87mte0g4g1.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=Emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=tor.kringeland@ntnu.no \
/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.