mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 1/7] ptxd_lib_code_signing: cs_get_ca(): improve error handling
Date: Fri, 9 Jul 2021 13:41:19 +0200	[thread overview]
Message-ID: <20210709114119.GA375046@pengutronix.de> (raw)
In-Reply-To: <20210709112632.cxtmg47citxjodxr@pengutronix.de>

On Fri, Jul 09, 2021 at 01:26:32PM +0200, Roland Hieber wrote:
> On Fri, Jul 09, 2021 at 09:42:09AM +0200, Michael Olbrich wrote:
> > On Thu, Jul 08, 2021 at 10:16:24PM +0200, Roland Hieber wrote:
> > > BTW, I like to get feedback mail as Cc into my inbox so I can keep a
> > > simple backlog of my still-to-be-done patches in addition to the
> > > PTXdist list mails, which go to a separate folder. (You often keep me in
> > > Cc, but somehow not always, but I think mutt should do this by default
> > > with the list-reply key binding …)
> > 
> > Not it doesn't. I mostly use 'list-reply'. This means relying to the list
> > and to any addresses in 'Mail-Followup-To'. An you don't add a
> > 'Mail-Followup-To' header.
> > 
> > If I remember it, I add you to Cc manually. For this mail I've used
> > 'group-reply'. As you can see, now the list in Cc and in my experience,
> > this increases the change that the list get's dropped at some point.
> > So I'd like to avoid doing that.
> 
> Yes, I think having myself in To and list in Cc is semantically correct.
> I always use 'group-reply' on lists and it never caused any problems,
> so I don't understand how you think the Cc address gets lost…?

I've had the problem in the past, that everything in Cc got lost.
But I have to admit, that it's been a while and I think it didn't happen on
community mailing-lists...

> > Newer versions of mutt have a 'group-chat-reply'. That would put both you
> > and the list in the 'To' field. But I'll need to wait until the servers
> > where I do most of my mail, are upgraded to bullseye.
> > 
> > But you should be able to add the Mail-Followup-To header. Mutt should
> > detect the mailing-list and add the header. I'd expect neomutt to do the
> > same. Maybe you have followup_to disabled?
> 
> Strange, I have followup_to set, but it doesn't generate the header.
> But I'm sending the mails via git-send-email anyways, which of course
> doesn't respect the mutt settings. So I guess I'll add it in the
> format.headers setting in my ptxdist/.git/config.

Good point about git. Let me try the group-reply for now. We'll see how
this goes. I just need to unmap the list-reply binding in the ptxdist
folder so I don't actually forget about this... :-).

Michael

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

      reply	other threads:[~2021-07-09 11:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 23:11 Roland Hieber
2021-06-27 23:11 ` [ptxdist] [PATCH v2 2/7] ptxd_lib_code_signing: introduce role groups Roland Hieber
2021-06-27 23:11 ` [ptxdist] [PATCH v2 3/7] templates/code-signing-provider: set up the 'imx-habv4-srk' role group Roland Hieber
2021-06-27 23:11 ` [ptxdist] [PATCH v2 4/7] templates/barebox-imx-habv4: use " Roland Hieber
2021-06-27 23:11 ` [ptxdist] [PATCH v2 5/7] host-ptx-code-signing-dev: version bump 0.4 -> 0.5 Roland Hieber
2021-06-27 23:11 ` [ptxdist] [PATCH v2 6/7] ptxd_lib_imx_hab: fix indentation Roland Hieber
2021-06-28  6:42   ` Michael Olbrich
2021-07-08 20:02     ` Roland Hieber
2021-07-09  6:53       ` Michael Olbrich
2021-07-09 10:12     ` Alexander Dahl
2021-07-09 10:41       ` Michael Olbrich
2021-07-16 11:38     ` Marc Kleine-Budde
2021-06-27 23:11 ` [ptxdist] [PATCH v2 7/7] ptxd_lib_code_signing: " Roland Hieber
2021-06-28  6:38 ` [ptxdist] [PATCH v2 1/7] ptxd_lib_code_signing: cs_get_ca(): improve error handling Michael Olbrich
2021-07-08 20:16   ` Roland Hieber
2021-07-09  7:42     ` Michael Olbrich
2021-07-09 11:26       ` Roland Hieber
2021-07-09 11:41         ` Michael Olbrich [this message]

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=20210709114119.GA375046@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@pengutronix.de \
    --subject='Re: [ptxdist] [PATCH v2 1/7] ptxd_lib_code_signing: cs_get_ca(): improve error handling' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox