git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 <velocifyer@velocifyer.com>, git@vger.kernel.org
Subject: Re: How do i get news of git releases
Date: Wed, 24 Sep 2025 11:51:19 -0700	[thread overview]
Message-ID: <xmqqcy7flm54.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD0t76v3XYgoLjZ-527EePQKihSNyA=AO0QjJHDy=u32JQ@mail.gmail.com> (Christian Couder's message of "Wed, 24 Sep 2025 10:38:17 +0200")

Christian Couder <christian.couder@gmail.com> writes:

> On Tue, Sep 23, 2025 at 9:42 PM
> <velocifyer@velocifyer.com> wrote:
>>
>> > The URL for each release points to the announcement email on the
>> > mailing list archive. That email contains the release notes.
>
>> If they already have the realease notes on the mailing list, why do they
>> not have a seprate "git-announce" mailing list with just the release
>> notes and other important announcements
>
> We try to keep everything on a single mailing list as much as possible
> to not split the community.

I do not see how the presence of an "announce-only" list would
fracture the community.  You could make such a list strictly
read-only for participants (i.e. only the list owners can send
things out, responses may be routed to those on whose behalf the
message was sent to the list, just to /dev/null, or perhaps to the
main list) for make it even clear that the secondary list is for
announce-only and any discussion about the items announced would
still happen on the main list.

It does take resources and coordination.  It won't happen without
anybody spending an extra effort.

Because those who would be writing the announce material for such a
secondary list are making enough efforts to help this community
thrive already, I do not particularly see the initial "why not a
separate announce list" question a very productive thing to think
about or respond to.  Unless the requestor is proposing to help such
an effort on continuous basis, that is.

> Also what is important depends a lot on the reader. For example
> Git for Windows or Git Rev News announcements might be important
> for some but not for others. So many people would have to sort
> things out anyway even if there were separate mailing lists.

That's very true.

      reply	other threads:[~2025-09-24 18:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 17:43 How do i get news of git releases 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-09-22 20:14 ` Jeff King
     [not found]   ` <1ff96277-c9e7-483e-ac98-b109b9603475@velocifyer.com>
2025-09-22 20:38     ` Jeff King
2025-09-22 21:16       ` Junio C Hamano
2025-09-22 21:35         ` Jeff King
2025-09-22 21:05   ` Junio C Hamano
2025-09-23  9:43 ` Christian Couder
2025-09-23 19:41   ` 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-09-24  8:38     ` Christian Couder
2025-09-24 18:51       ` 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

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

  git send-email \
    --in-reply-to=xmqqcy7flm54.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=velocifyer@velocifyer.com \
    /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.
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 NNTP newsgroup(s).