From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mrep: Set From header according to To/Cc header
Date: Mon, 30 Mar 2020 14:16:02 +0200 [thread overview]
Message-ID: <20200330121602.yJGimP2RBpY4VHfObAZUkAwHLeCXxxtJ93Pu2bBM9G8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-173@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
New comment by Duncaen on mblaze repository
https://github.com/leahneukirchen/mblaze/pull/173#issuecomment-605959471
Comment:
`magrep` with `-a` would be a good instead of grep, but it only matches all headers or one header at a time.
```
$ magrep -ha "to:mail@duncano.de|administrator@duncano.de" 100
to: administrator@duncano.de
$ mhdr -h to 100
Duncan Overbruck <administrator@duncano.de>
```
Edit: nvm, this doesn't really solve the problem, but might be better than a plain grep if someone messes with comments in addresses etc.
next prev parent reply other threads:[~2020-03-30 12:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-173@inbox.vuxu.org>
2020-03-30 10:28 ` leahneukirchen
2020-03-30 11:22 ` nmeum
2020-03-30 11:59 ` leahneukirchen
2020-03-30 12:05 ` Duncaen
2020-03-30 12:08 ` Duncaen
2020-03-30 12:09 ` Duncaen
2020-03-30 12:16 ` Duncaen [this message]
2020-03-30 12:54 ` nmeum
2020-03-30 13:04 ` leahneukirchen
2020-03-30 14:49 ` nmeum
2020-03-30 14:56 ` leahneukirchen
2020-03-30 17:37 ` [PR PATCH] [Updated] " nmeum
2020-03-30 17:37 ` nmeum
2020-03-30 17:46 ` [PR PATCH] [Updated] " nmeum
2020-03-30 17:48 ` nmeum
2020-03-30 17:50 ` leahneukirchen
2020-03-30 17:56 ` nmeum
2020-03-30 17:56 ` nmeum
2020-03-30 17:56 ` nmeum
2020-03-30 17:57 ` nmeum
2020-03-30 18:02 ` leahneukirchen
2020-03-30 18:04 ` leahneukirchen
2020-03-30 18:44 ` nmeum
2020-04-20 13:43 ` [PR PATCH] [Updated] " nmeum
2020-04-20 13:44 ` nmeum
2020-04-20 13:50 ` nmeum
2020-04-20 13:51 ` nmeum
2020-04-20 13:55 ` nmeum
2020-04-20 13:55 ` nmeum
2020-04-20 13:58 ` leahneukirchen
2020-04-20 14:08 ` [PR PATCH] [Updated] " nmeum
2020-04-20 14:12 ` nmeum
2020-04-20 14:20 ` [PR PATCH] [Updated] " nmeum
2020-04-20 14:25 ` nmeum
2020-05-20 1:40 ` xelxebar
2020-05-20 1:41 ` xelxebar
2020-05-23 13:43 ` leahneukirchen
2020-05-23 14:02 ` leahneukirchen
2020-09-06 14:30 ` [PR PATCH] [Closed]: " leahneukirchen
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=20200330121602.yJGimP2RBpY4VHfObAZUkAwHLeCXxxtJ93Pu2bBM9G8@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).