From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Nix <nix@esperi.org.uk>
Cc: jes@trained-monkey.org, linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/6] mdadm: remove ANNOUNCEs
Date: Fri, 8 Mar 2024 08:35:42 +0100 [thread overview]
Message-ID: <20240308083542.00006121@linux.intel.com> (raw)
In-Reply-To: <87jzme9otb.fsf@esperi.org.uk>
On Thu, 07 Mar 2024 13:03:28 +0000
Nix <nix@esperi.org.uk> wrote:
> On 28 Feb 2024, Mariusz Tkaczyk spake thusly:
>
> > On Wed, 28 Feb 2024 14:40:22 +0000
> > Nix <nix@esperi.org.uk> wrote:
> >
> >> 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".
> >
> > Agree, we have to maintain it but in simpler form. I will create CHANGELOG
> > instead. I will copy the content of those files to changelog, with some
> > modifications.
>
> They are a bit of a mess at the top level though. Maybe move them into
> misc/ or a new doc/ or something?
>
In other projects files like that are handled in main directory. I should
consider moving code into "/src" directory, udev stuff into "/udev", man files
into "/man" instead.
If you would like to try create some patches to help me with cleanup I will be
appreciated!
For now, I'm working on following files:
- README.md - general instructions; what is it, how to contribute, etc.
- MAINTAINERS.md - instructions for maintainers.
- CHANGELOG.md - release stuff.
I choose markdown because it is most popular and it gives ".md" it the name:)
I should send them to review next week.
Thanks,
Mariusz
next prev parent reply other threads:[~2024-03-08 7:35 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
2024-02-28 15:40 ` Mariusz Tkaczyk
2024-03-07 13:03 ` Nix
2024-03-08 7:35 ` Mariusz Tkaczyk [this message]
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=20240308083542.00006121@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).