unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Platon Pronko <platon7pronko@gmail.com>
To: help-gnu-emacs@gnu.org, uzibalqa <uzibalqa@proton.me>
Subject: Re: Making new menu after Tools using keymap-set-after
Date: Wed, 19 Jul 2023 21:25:11 +0400	[thread overview]
Message-ID: <3436214f-8a4b-e7d0-d614-9f9be087f1b9@gmail.com> (raw)
In-Reply-To: <79bs5-kQmXMrrO6YFAlJeoE64_mYHFGuGgofaYbY388ZDrdUclOYUDqzqTjo6oXa5AeO11hdrgORJL6ZJs-5i1w3KCyLOBNm36Oh_b_TPzA=@proton.me>

On 2023-07-19 21:11, uzibalqa wrote:
> If one does
> 
> git clone -b master git://git.sv.gnu.org/emacs.git
> 
> they would have no clue.

Surely you can get a commit hash from your clone? `git log -1` or `git show` should both work. And said commit hash would quite specifically point to the exact version of the code you are using.

-- 
Best regards,
Platon Pronko
PGP 2A62D77A7A2CB94E




  reply	other threads:[~2023-07-19 17:25 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 16:04 Making new menu after Tools using keymap-set-after uzibalqa
2023-07-18 16:29 ` Eli Zaretskii
2023-07-18 16:56   ` uzibalqa
2023-07-18 17:12     ` Eli Zaretskii
2023-07-18 17:29       ` uzibalqa
2023-07-18 18:28         ` Eli Zaretskii
2023-07-18 18:45           ` uzibalqa
2023-07-18 19:02             ` Eli Zaretskii
2023-07-18 19:26               ` uzibalqa
2023-07-19  2:25                 ` Eli Zaretskii
2023-07-19  8:08                   ` uzibalqa
2023-07-19  9:10                     ` Robert Pluim
2023-07-19 15:58                       ` uzibalqa
2023-07-19 16:33                         ` Eli Zaretskii
2023-07-19 16:37                           ` uzibalqa
2023-07-19 16:44                           ` Robert Pluim
2023-07-19 16:54                             ` uzibalqa
2023-07-19 17:07                               ` Robert Pluim
2023-07-19 17:11                                 ` uzibalqa
2023-07-19 17:25                                   ` Platon Pronko [this message]
2023-07-19 17:34                                     ` uzibalqa
2023-07-20  3:17                                       ` Platon Pronko
2023-07-19 17:28                               ` [External] : " Drew Adams
2023-07-19 17:37                                 ` uzibalqa
2023-07-19 19:00                                   ` Drew Adams
2023-07-19 19:08                                     ` uzibalqa
2023-07-20  3:32                                       ` Platon Pronko
2023-07-20  8:43                                         ` uzibalqa
2023-07-19 21:00                           ` uzibalqa
2023-07-18 20:42             ` [External] : " Drew Adams
2023-07-18 20:55               ` uzibalqa
2023-07-18 21:40                 ` uzibalqa
2023-07-19 12:11                   ` Eli Zaretskii
2023-07-19 11:58               ` Eli Zaretskii
2023-07-19 14:18                 ` Drew Adams
2023-07-18 20:49       ` uzibalqa
2023-07-19 12:00         ` 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=3436214f-8a4b-e7d0-d614-9f9be087f1b9@gmail.com \
    --to=platon7pronko@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=uzibalqa@proton.me \
    /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.
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).