All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Lars Kurth <lars.kurth@citrix.com>, xen-devel@lists.xenproject.org
Cc: Felipe Huici <felipe.huici@neclab.eu>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	Florian Schmidt <florian.schmidt@neclab.eu>,
	Jan Beulich <jbeulich@suse.com>,
	Simon Kuenzer <simon.kuenzer@neclab.eu>
Subject: Re: [Xen-devel] [PATCH] get_maintainers.pl: Enable running the script on unikraft repos
Date: Fri, 16 Aug 2019 11:55:16 +0100	[thread overview]
Message-ID: <200d8505-6822-3d9f-98fe-e8d7e09d00b8@arm.com> (raw)
In-Reply-To: <4b535bb616f62ad685fef0f06d3b5138b1539688.1565951950.git.lars.kurth@citrix.com>

Hi Lars,

On 16/08/2019 11:42, Lars Kurth wrote:
> Unikraft repos follow the same syntax as xen.git with the
> following exceptions:
> * MAINTAINERS files are called MAINTAINERS.md
> * M: ... etc blocks are preceded by whitespaces for rendering as
>    markup files

There is an other difference. The "fallback" category is "UNIKRAFT GENERAL" and 
not "THE REST".

> 
> This change will
> - load MAINTAINERS.md if MAINTAINERS is not present
> - deal with indented M: ... blocks

One process question. Does it mean Unikraft folks will have to checkout Xen in 
order to use {add, get}_maintainers.pl? If so, would it make sense to have 
add_maintainers.pl and script_maintainers.pl in a separate repo that can be 
added as submodule?

> 
> Signed-off-by: Lars Kurth <lars.kurth@citrix.com>
> ---
> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
> Cc: George Dunlap <George.Dunlap@eu.citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> Cc: Jan Beulich <jbeulich@suse.com>
> Cc: Julien Grall <julien.grall@arm.com>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: Stefano Stabellini <sstabellini@kernel.org>
> Cc: Tim Deegan <tim@xen.org>
> Cc: Wei Liu <wl@xen.org>
> 
> CC: Simon Kuenzer <simon.kuenzer@neclab.eu>
> CC: Florian Schmidt <florian.schmidt@neclab.eu>
> CC: Felipe Huici <felipe.huici@neclab.eu>
> ---
>   scripts/get_maintainer.pl | 14 ++++++++++----
>   1 file changed, 10 insertions(+), 4 deletions(-)
> 
> diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
> index f1e9c904ee..bdb09f8f65 100755
> --- a/scripts/get_maintainer.pl
> +++ b/scripts/get_maintainer.pl
> @@ -284,12 +284,18 @@ if (!top_of_tree($xen_path)) {
>   my @typevalue = ();
>   my %keyword_hash;
>   
> -open (my $maint, '<', "${xen_path}MAINTAINERS")
> -    or die "$P: Can't open MAINTAINERS: $!\n";
> +my $maint;
> +my $maintainers_file = "MAINTAINERS";
> +if (! open ($maint, '<', ${xen_path}.$maintainers_file)) {
> +    $maintainers_file = "MAINTAINERS.md";
> +    open ($maint, '<', ${xen_path}.$maintainers_file)
> +        or die "$P: Can't open MAINTAINERS or MAINTAINERS.md: $!\n";
> +}
> +
>   while (<$maint>) {
>       my $line = $_;
>   
> -    if ($line =~ m/^([A-Z]):\s*(.*)/) {
> +    if ($line =~ m/^\s*([A-Z]):\s*(.*)/) {

As you allow space before the blocks M:, would not this catch the example at the 
beginning of the file?

	M: Mail patches to: FullName <address@domain>
	R: Designated reviewer: FullName <address@domain>

>   	my $type = $1;
>   	my $value = $2;
>   
> @@ -421,7 +427,7 @@ foreach my $file (@ARGV) {
>       }
>       if ($from_filename) {
>   	push(@files, $file);
> -	if ($file ne "MAINTAINERS" && -f $file && ($keywords || $file_emails)) {
> +	if ($file ne $maintainers_file && -f $file && ($keywords || $file_emails)) {
>   	    open(my $f, '<', $file)
>   		or die "$P: Can't open $file: $!\n";
>   	    my $text = do { local($/) ; <$f> };
> 

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-08-16 10:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 10:42 [Xen-devel] [PATCH] get_maintainers.pl: Enable running the script on unikraft repos Lars Kurth
2019-08-16 10:55 ` Julien Grall [this message]
2019-08-16 11:17   ` Anthony PERARD
2019-08-16 12:05     ` Lars Kurth
2019-08-16 12:09       ` Paul Durrant
2019-08-16 12:20         ` Lars Kurth
2019-08-16 12:28           ` Paul Durrant
2019-08-16 11:41   ` Lars Kurth
2019-08-16 13:22     ` Julien Grall

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=200d8505-6822-3d9f-98fe-e8d7e09d00b8@arm.com \
    --to=julien.grall@arm.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=felipe.huici@neclab.eu \
    --cc=florian.schmidt@neclab.eu \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lars.kurth@citrix.com \
    --cc=simon.kuenzer@neclab.eu \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.