list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <>
To: Fernando Ramos <>
Cc: Junio C Hamano <>,
Subject: Re: [ANNOUNCE] Git v2.37.0-rc2
Date: Sun, 26 Jun 2022 17:03:14 -0400	[thread overview]
Message-ID: <YrjJkuX6diZiF/> (raw)
In-Reply-To: <Yrii4Wj+c0YuQy61@zacax395.localdomain>

On Sun, Jun 26, 2022 at 08:18:09PM +0200, Fernando Ramos wrote:

> On 22/06/22 12:32PM, Junio C Hamano wrote:
> >  * "vimdiff[123]" mergetool drivers have been reimplemented with a
> >    more generic layout mechanism.
> Hi. Maybe because this is my first contribution to git I was strangely excited
> and decided to create a small blog post describing how the new mechanism works.
> [...]
> PS: Please let me know if this type of message is not appropriate for this
> mailing list and I will never do it again... I just thought it might be good to
> explain the new feature in a blog post to prevent it from going unnoticied
> considering how "hidden" the new configuration variable is. Thanks!

No, this is very cool. Describing your changes to the greater world is
very welcome, and letting people here know about it is good.

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 can imagine that Junio
especially gets a lot of emails. :) So for something like this that's
more of general interest than an email to a specific person, I'd usually
either bump them down to "cc" rather than "to" (using the list address
for "to"), or even remove them entirely from the headers (and they may
read it from the general list like everyone else).

Congratulations on making your first contribution to Git!


  reply	other threads:[~2022-06-26 21:05 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 [this message]
2022-06-27  6:00     ` Fernando Ramos
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=YrjJkuX6diZiF/ \ \ \ \ \

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