discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 0/2] piem-b4-am: Add --cc-trailers
Date: Sun, 15 May 2022 22:40:39 -0400	[thread overview]
Message-ID: <20220516024041.205178-1-kyle@kyleam.com> (raw)

  [1/2] piem-b4-am: Move trailer-related options to dedicated section
  [2/2] piem-b4-am: Add --cc-trailers

 piem-b4.el | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

base-commit: cbddebaa8e535e94d95510f02ebe8152c5d1a0b8

             reply	other threads:[~2022-05-16  2:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16  2:40 Kyle Meyer [this message]
2022-05-16  2:40 ` [PATCH 1/2] piem-b4-am: Move trailer-related options to dedicated section Kyle Meyer
2022-05-16  2:40 ` [PATCH 2/2] piem-b4-am: Add --cc-trailers Kyle Meyer

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:

  List information: https://git.kyleam.com/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220516024041.205178-1-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \


* 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


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).