From: Jean Delvare <jdelvare@suse.de>
To: Joe Perches <joe@perches.com>
Cc: Andy Whitcroft <apw@canonical.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: False positive from checkscript: git git://...
Date: Thu, 29 Oct 2020 16:11:44 +0100 [thread overview]
Message-ID: <20201029161144.3c7a4fb1@endymion> (raw)
In-Reply-To: <24f8766403f881d4f56a9b721f29b6ee5d1173e2.camel@perches.com>
On Thu, 29 Oct 2020 07:55:25 -0700, Joe Perches wrote:
> On Thu, 2020-10-29 at 14:32 +0100, Jean Delvare wrote:
> > WARNING: Possible repeated word: 'git'
> > #20: FILE: MAINTAINERS:5289:
> > +T: git git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git dmi-for-next
> >
> > Obviously that's going to happen a lot as this is actually the proper
> > way to list a git tree in that file. Could you please add an exception
> > for that case?
>
> Already done in -next
Perfect, thank you very much.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2020-10-29 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 13:32 False positive from checkscript: git git:// Jean Delvare
2020-10-29 14:55 ` Joe Perches
2020-10-29 15:11 ` Jean Delvare [this message]
2020-10-29 15:41 ` Joe Perches
2020-10-29 15:50 ` Dwaipayan Ray
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=20201029161144.3c7a4fb1@endymion \
--to=jdelvare@suse.de \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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