list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Fernando Ramos <>
To: Jeff King <>
Cc: Junio C Hamano <>,
Subject: Re: [ANNOUNCE] Git v2.37.0-rc2
Date: Mon, 27 Jun 2022 08:00:55 +0200	[thread overview]
Message-ID: <YrlHjtyratGlxs/D@zacax395.localdomain> (raw)
In-Reply-To: <YrjJkuX6diZiF/>

On 22/06/26 05:03PM, Jeff King wrote:
> One thing I would suggest, though: many folks on the list use the
> presence of their email in the "to" or "cc" of a message to help
> prioritize (i.e., to see responses directly to them which may need a
> response, versus general list chatter).

You are completely right. I should have noticed this before sending the message
(I also use to/cc for priorization and my message obviously did not require a
reply from Junio). I'll pay more attention in the future. Thanks!

  reply	other threads:[~2022-06-27  6:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 19:32 Junio C Hamano
2022-06-26 18:18 ` Fernando Ramos
2022-06-26 21:03   ` Jeff King
2022-06-27  6:00     ` Fernando Ramos [this message]
2022-06-27  8:32   ` Junio C Hamano

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:

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

  git send-email \
    --in-reply-to=YrlHjtyratGlxs/D@zacax395.localdomain \ \ \ \ \

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