From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, 36167@debbugs.gnu.org
Subject: bug#36167: [PATCH] Replace [0-9a-fA-F] with [[:xdigit:]]
Date: Wed, 12 Jun 2019 20:09:09 +0300 [thread overview]
Message-ID: <1560359349.5452.1@yandex.ru> (raw)
In-Reply-To: <83blz2927i.fsf@gnu.org>
В Ср, июн 12, 2019 at 19:51, Eli Zaretskii <eliz@gnu.org>
написал:
>> Date: Wed, 12 Jun 2019 19:39:26 +0300
>> From: Konstantin Kharlamov <hi-angel@yandex.ru>
>> Cc: rpluim@gmail.com, 36167@debbugs.gnu.org
>>
>> > When you change 400 files, no one will expect you to mention each
>> > instance, it's enough to describe the change itself and say "in
>> all
>> > files" or somesuch.
>>
>> Can I do that for 20 files?
>
> Borderline, IMO.
>
> Can't the command you use output the list of functions or at least
> files where it made the changes? Then you could massage that list
> into a log message.
Getting the list of files is trivial, I can just copy them from a `git
diff --name-only` or some such. Getting the list of modified functions
in code is harder.
Anyway, I'll try making some function later to apply recursively the
(add-change-log-entry-other-window), that sounds good to have in
general.
next prev parent reply other threads:[~2019-06-12 17:09 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 11:59 bug#36167: [PATCH] Replace manually crafted hex regexes with [[:xdigit:]] Konstantin Kharlamov
2019-06-11 12:03 ` bug#36167: Acknowledgement ([PATCH] Replace manually crafted hex regexes with [[:xdigit:]]) Konstantin Kharlamov
2019-06-11 12:29 ` bug#36167: [PATCH] Replace [0-9a-fA-F] with [[:xdigit:]] Konstantin Kharlamov
2019-06-11 13:03 ` Robert Pluim
2019-06-11 13:17 ` Konstantin Kharlamov
2019-06-11 13:30 ` Robert Pluim
2019-06-12 0:29 ` Konstantin Kharlamov
2019-06-12 2:42 ` Eli Zaretskii
2019-06-12 8:21 ` Robert Pluim
2019-06-12 11:19 ` Konstantin Kharlamov
2019-06-12 14:55 ` Eli Zaretskii
2019-06-12 16:39 ` Konstantin Kharlamov
2019-06-12 16:51 ` Eli Zaretskii
2019-06-12 17:09 ` Konstantin Kharlamov [this message]
2019-06-12 21:33 ` Lars Ingebrigtsen
2019-06-12 21:39 ` Lars Ingebrigtsen
2019-06-12 22:17 ` Andreas Schwab
2019-06-12 22:22 ` Lars Ingebrigtsen
2019-06-12 22:48 ` Konstantin Kharlamov
2019-06-11 13:32 ` npostavs
2019-06-11 14:36 ` Eli Zaretskii
2019-06-11 14:26 ` bug#36167: [PATCH] Replace manually crafted hex regexes " Paul Eggert
2019-06-11 14:37 ` Konstantin Kharlamov
2019-06-11 15:37 ` Paul Eggert
2019-06-11 16:31 ` Mattias Engdegård
2019-06-11 16:50 ` Drew Adams
2019-06-11 17:04 ` Eli Zaretskii
2019-06-11 17:18 ` Paul Eggert
2019-06-11 17:32 ` Eli Zaretskii
2019-06-11 17:19 ` Drew Adams
2019-06-11 17:34 ` Eli Zaretskii
2019-06-11 17:50 ` npostavs
2019-06-11 17:53 ` Eli Zaretskii
2019-06-11 18:14 ` Eli Zaretskii
2019-06-11 19:56 ` Andy Moreton
2019-06-12 2:30 ` Eli Zaretskii
2019-06-12 11:44 ` Andy Moreton
2019-06-12 16:07 ` Eli Zaretskii
2019-06-13 0:18 ` bug#36167: [PATCH v2] Replace manually crafted hex regexes wth [[:xdigit:]] Konstantin Kharlamov
2019-07-06 8:04 ` Eli Zaretskii
2019-07-08 9:34 ` bug#36167: [PATCH v2] Replace manually crafted hex regexes with [[:xdigit:]] Konstantin Kharlamov
2019-07-08 12:11 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1560359349.5452.1@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=36167@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rpluim@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 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.