From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: 35368@debbugs.gnu.org
Subject: bug#35368: Acknowledgement ([PATCH] Do potentially destructive operations in prepare-commit-msg)
Date: Tue, 23 Apr 2019 11:43:16 +0100 [thread overview]
Message-ID: <875zr5f1dn.fsf@tcd.ie> (raw)
In-Reply-To: <1556013426.24472.0@yandex.ru> (Konstantin Kharlamov's message of "Tue, 23 Apr 2019 12:57:06 +0300")
Konstantin Kharlamov <hi-angel@yandex.ru> writes:
> Oh, and while on it: I'm thinking also about automatically filling the default
> commit template (i.e. files changed, functions changed — can be inferred for C).
> I'm wondering, which language would it be acceptable to write hook in? Python?
Why not Elisp? IIUC this already exists as add-change-log-entry.
--
Basil
next prev parent reply other threads:[~2019-04-23 10:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 20:03 bug#35368: [PATCH] Do potentially destructive operations in prepare-commit-msg Konstantin Kharlamov
2019-04-21 20:17 ` bug#35368: [PATCH v2] " Konstantin Kharlamov
2019-05-14 17:33 ` npostavs
2019-05-14 21:22 ` Konstantin Kharlamov
2019-05-14 22:09 ` Noam Postavsky
2019-05-14 22:15 ` Konstantin Kharlamov
2019-05-14 22:26 ` bug#35368: [PATCH v3] " Konstantin Kharlamov
2019-05-15 17:40 ` npostavs
2019-05-15 21:25 ` bug#35368: [PATCH v4] " Konstantin Kharlamov
2019-05-17 0:35 ` Noam Postavsky
2019-05-17 0:39 ` Konstantin Kharlamov
2019-05-15 21:28 ` bug#35368: [PATCH v3] " Konstantin Kharlamov
[not found] ` <handler.35368.B.155587702222113.ack@debbugs.gnu.org>
2019-04-23 9:57 ` bug#35368: Acknowledgement ([PATCH] Do potentially destructive operations in prepare-commit-msg) Konstantin Kharlamov
2019-04-23 10:40 ` Eli Zaretskii
2019-04-23 10:43 ` Basil L. Contovounesios [this message]
2019-04-23 11:00 ` Konstantin Kharlamov
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=875zr5f1dn.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=35368@debbugs.gnu.org \
--cc=hi-angel@yandex.ru \
/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.