From: Noam Postavsky <npostavs@gmail.com>
To: Konstantin Kharlamov <Hi-Angel@yandex.ru>
Cc: 35368@debbugs.gnu.org
Subject: bug#35368: [PATCH v4] Do potentially destructive operations in prepare-commit-msg
Date: Thu, 16 May 2019 20:35:13 -0400 [thread overview]
Message-ID: <87ef4xex4u.fsf@gmail.com> (raw)
In-Reply-To: <20190515212553.5319-1-Hi-Angel@yandex.ru> (Konstantin Kharlamov's message of "Thu, 16 May 2019 00:25:53 +0300")
tags 35368 fixed
close 35368
quit
Konstantin Kharlamov <Hi-Angel@yandex.ru> writes:
> * build-aux/git-hooks/prepare-commit-msg: if someone occasionally puts
> + # catch the case when someone ran git-commit with -s option,
Capitalized and pushed to emacs-26.
2bdc419f51 2019-05-16T20:25:32-04:00 "Do potentially destructive operations in prepare-commit-msg"
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=2bdc419f51630eb433deb139da67e419000c7694
next prev parent reply other threads:[~2019-05-17 0:35 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 [this message]
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
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=87ef4xex4u.fsf@gmail.com \
--to=npostavs@gmail.com \
--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.