From: Nix <nix@esperi.org.uk>
To: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
Cc: jes@trained-monkey.org, linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/6] mdadm: remove ANNOUNCEs
Date: Wed, 28 Feb 2024 14:40:22 +0000 [thread overview]
Message-ID: <871q8wsld5.fsf@esperi.org.uk> (raw)
In-Reply-To: <20240223145146.3822-2-mariusz.tkaczyk@linux.intel.com> (Mariusz Tkaczyk's message of "Fri, 23 Feb 2024 15:51:41 +0100")
On 23 Feb 2024, Mariusz Tkaczyk uttered the following:
> Release stuff is not necessary in repository. Remove it.
... it's actually pretty useful to have the ANNOUNCEs there for people
building from the repo. Given that the changelog is not updated, having
a summary of changes *somewhere* without having to grovel around in
mailing list archives seems like a thing that shouldn't just be thrown
out as "not necessary".
next prev parent reply other threads:[~2024-02-28 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 14:51 [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 1/6] mdadm: remove ANNOUNCEs Mariusz Tkaczyk
2024-02-28 14:40 ` Nix [this message]
2024-02-28 15:40 ` Mariusz Tkaczyk
2024-03-07 13:03 ` Nix
2024-03-08 7:35 ` Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 2/6] mdadm: remove TODO Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 3/6] mdadm: remove makedist Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 4/6] mdadm: remove mdadm.spec Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 5/6] mdadm: remove mkinitramfs stuff Mariusz Tkaczyk
2024-02-23 14:51 ` [PATCH 6/6] mdadm: move documentation to folder Mariusz Tkaczyk
2024-02-29 14:11 ` [PATCH 0/6] Repository cleanup Mariusz Tkaczyk
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=871q8wsld5.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.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).