git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Fernando Ramos <greenfoo@u92.eu>
Cc: git@vger.kernel.org, Christian Couder <christian.couder@gmail.com>
Subject: Re: [ANNOUNCE] Git v2.37.0-rc2
Date: Mon, 27 Jun 2022 01:32:09 -0700	[thread overview]
Message-ID: <xmqqv8smqzg6.fsf@gitster.g> (raw)
In-Reply-To: Yrii4Wj+c0YuQy61@zacax395.localdomain

Fernando Ramos <greenfoo@u92.eu> writes:

> 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.
>
> There is no javascript nor tracking nor ads... just good old html/css/pngs
> explaining how and when to use `mergetool.vimdiff.layout`:
>
>   https://u92.eu/blog/git-vimdiff/
>
> Hope someone finds this useful :)
>
> 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!

You may want to also tell Git Rev News editors (Christian Cc'ed)
about the blog post page, I think they have a list of Git related
readings in each edition.

Thanks for an interesting feature.

      parent reply	other threads:[~2022-06-27  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 19:32 [ANNOUNCE] Git v2.37.0-rc2 Junio C Hamano
2022-06-26 18:18 ` Fernando Ramos
2022-06-26 21:03   ` Jeff King
2022-06-27  6:00     ` Fernando Ramos
2022-06-27  8:32   ` Junio C Hamano [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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqv8smqzg6.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=greenfoo@u92.eu \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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