Topics suggested for this edition:

from @felipec:

Shouldn't the [report](https://lore.kernel.org/git/742df4c2-2bc5-8a4b-8de1-cd5e48718398@redhat.com/)
about git pull warning and the subsequent patch series trying to improve the situation be worthwhile to mention?

This BTW revives the [old discussion](https://lore.kernel.org/git/5363BB9F.40102@xiplink.com/), so it's
interesting something that wasn't fixed in 2014 is still biting us today.

from @PhilipOakley:

Another thought for potential inclusions (given the `git pull` comment) could the the new and changed `config`
variables (documentation & code) that have graduated to `next`/`main` so that these new / changed features and
defaults become known. Probably something that can be deferred to the next Git Rev News

Shouldn't the proposal to include a reftable library be worth mentioning?

@felipec thanks for the suggestion! Usually the main issue is that I don't have time to write about all the interesting things going on, and it doesn't happen often that someone else writes an article about something going on. But I think it's ok. No one really expects us to summarize everything.

Let's not forget to talk about the Outreachy interns who were accepted and started working recently. They have also posted to the mailing list about their blog.

Also in a short news I'd like to mention @felipec 's New sharness/test vim syntax.

The thread where a .vimrc loader is included in addition to the syntax file might be more newsworthy.

Outreachy interns info has been added in 9a73249.

There's also the blog post about mergetools that prompted me to write the patches about mergetools.autoMerge, which in turn prompted a new blog post explaining the new situation:

Mergetools: strop doing three-way merges!

The current version seems a bit thin to me.

These are some of the topics that come to mind.

• git pull improvements
• autotool.mergetool
• possible git bisect run --recheck
• sharness syntax
• proposed project-wide .vimrc
• Hashed mailmap
• report unborn branches on empty clone
• Parallel checkout
• Allow push @

I could write about some of these if you want. The I'm really interested in is the "git pull" one, since I think that's the one that has more impact towards users, has been an issue for more than a decade, and also I've worked a lot on that one.

@felipec : Will you add the article about mergetools?

I have added my links to articles and tools in ab08ad9 . I skipped mentioning GitHub Codespaces because for now it is invite-only feature.

@jnareb thanks for your links!

@felipec I am very late, so the publication will be delayed by 2 or 3 days. I will write an article anyway before sending the draft to the mailing list, so don't worry about the current version being too thin. You are welcome to contribute articles or short news too. Please use PRs for that.

@felipec if you write articles, please consider writing first about things that have settled for a few weeks, rather than ongoing, and things that promote developers, reviewers and helpers (as per our goals in https://git.github.io/rev_news/rev_news/).

Draft sent (https://lore.kernel.org/git/CAP8UFD0uKV+PK6wkyyNV=--SBFOE8MGZRUdXCmMeGD4x3emOug@mail.gmail.com/). Sorry for the delay everyone! Let's publish this edition on Saturday December 26th!

@mjaix great, thanks!

Published and announced in:

https://lore.kernel.org/git/CAP8UFD2V5EdY2VBgP0Ah7BNri_znrGCMQ7LLwhATzJ5PaEymqQ@mail.gmail.com/