From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 35368@debbugs.gnu.org
Subject: bug#35368: [PATCH v2] Do potentially destructive operations in prepare-commit-msg
Date: Wed, 15 May 2019 01:15:38 +0300 [thread overview]
Message-ID: <1557872138.32614.1@yandex.ru> (raw)
In-Reply-To: <87k1esg02j.fsf@gmail.com>
В Вт, мая 14, 2019 at 18:09, Noam Postavsky <npostavs@gmail.com>
написал:
> Konstantin Kharlamov <hi-angel@yandex.ru> writes:
>
>> I took that part of code from the current `commit-msg`. And if you
>> think it's unnecessary, then it's unnecessary as well in the current
>> `commit-msg`.
>
> You didn't take the awk code in commit-msg that actually uses the
> at_sign and cent_sign variables, so I don't think that follows.
Oh, right, I see, thanks. Let me fix this…
next prev parent reply other threads:[~2019-05-14 22:15 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 [this message]
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
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
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=1557872138.32614.1@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=35368@debbugs.gnu.org \
--cc=npostavs@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).