From: "Alex Bennée" <alex.bennee@linaro.org>
To: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
hpoussin@reactos.org,
Aleksandar Markovic <amarkovic@wavecomp.com>,
aleksandar.rikalo@rt-rk.com, philmd@redhat.com,
aurelien@aurel32.net
Subject: Re: [PATCH 1/5] MAINTAINERS: Add a section on git infrastructure
Date: Tue, 12 Nov 2019 16:57:03 +0000 [thread overview]
Message-ID: <87tv79823k.fsf@linaro.org> (raw)
In-Reply-To: <1573240249-6966-2-git-send-email-aleksandar.markovic@rt-rk.com>
Aleksandar Markovic <aleksandar.markovic@rt-rk.com> writes:
> From: Aleksandar Markovic <amarkovic@wavecomp.com>
>
> There should be a patient person maintaining gory details of
> git-related files, and there is no better person for that role
> than Philippe. Alex should be the reviewer for some relations
> with gitdm.
I'm not sure about this. The .gitignore files are best updated by people
responsible for the various parts of the tree. Once out-of-tree builds
become standard we should be able to eliminate them all together. As far
as .mailmap is concerned I think people are quite capable of updating it
themselves without putting the changes through a maintainer tree.
>
> Signed-off-by: Aleksandar Markovic <amarkovic@wavecomp.com>
> ---
> MAINTAINERS | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4964fbb..be43ccb 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2664,6 +2664,23 @@ M: Daniel P. Berrange <berrange@redhat.com>
> S: Odd Fixes
> F: scripts/git-submodule.sh
>
> +GIT infrastructure
> +M: Philippe Mathieu-Daudé <philmd@redhat.com>
> +R: Alex Bennée <alex.bennee@linaro.org>
> +S: Maintained
> +F: .mailmap
> +F: scripts/git.orderfile
> +F: .gitignore
> +F: tests/fp/.gitignore
> +F: tests/fp/berkeley-softfloat-3/.gitignore
> +F: tests/fp/berkeley-testfloat-3/.gitignore
> +F: tests/migration/.gitignore
> +F: tests/multiboot/.gitignore
> +F: tests/qemu-iotests/.gitignore
> +F: tests/tcg/.gitignore
> +F: tests/uefi-test-tools/.gitignore
> +F: ui/keycodemapdb/tests/.gitignore
> +
> Sphinx documentation configuration and build machinery
> M: Peter Maydell <peter.maydell@linaro.org>
> S: Maintained
--
Alex Bennée
next prev parent reply other threads:[~2019-11-12 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 19:10 [PATCH 0/5] MAINTAINERS: Fine adjustment for (mostly mips) content Aleksandar Markovic
2019-11-08 19:10 ` [PATCH 1/5] MAINTAINERS: Add a section on git infrastructure Aleksandar Markovic
2019-11-12 16:57 ` Alex Bennée [this message]
2019-11-12 20:57 ` Aleksandar Markovic
2019-11-08 19:10 ` [PATCH 2/5] MAINTAINERS: Add a section on UI translation Aleksandar Markovic
2019-11-08 19:10 ` [PATCH 3/5] MAINTAINERS: Adjust maintainership for Fulong 2E board Aleksandar Markovic
2019-11-08 19:10 ` [PATCH 4/5] MAINTAINERS: Adjust maintainership for Malta board Aleksandar Markovic
2019-11-11 10:12 ` Aurelien Jarno
2019-11-11 10:13 ` Aurelien Jarno
2019-11-08 19:10 ` [PATCH 5/5] MAINTAINERS: Adjust maintainership for R4000 systems Aleksandar Markovic
2019-11-11 10:13 ` Aurelien Jarno
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=87tv79823k.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aleksandar.markovic@rt-rk.com \
--cc=aleksandar.rikalo@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=hpoussin@reactos.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).