From: Richard Weinberger <richard@nod.at>
To: Joe Perches <joe@perches.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Update UBI/UBIFS git tree location
Date: Thu, 16 May 2019 00:42:14 +0200 (CEST) [thread overview]
Message-ID: <494585403.60051.1557960134909.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <391f21cf5f04c61b75e739f67c8a308864b4e68c.camel@perches.com>
----- Ursprüngliche Mail -----
> Von: "Joe Perches" <joe@perches.com>
> An: "richard" <richard@nod.at>, "linux-mtd" <linux-mtd@lists.infradead.org>
> CC: "linux-kernel" <linux-kernel@vger.kernel.org>
> Gesendet: Donnerstag, 16. Mai 2019 00:29:48
> Betreff: Re: [PATCH] MAINTAINERS: Update UBI/UBIFS git tree location
> On Wed, 2019-05-15 at 22:04 +0200, Richard Weinberger wrote:
>> Linus asked to use kernel.org.
>>
>> Signed-off-by: Richard Weinberger <richard@nod.at>
>> ---
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 5c38f21aee78..ba428cd613b8 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -15879,7 +15879,7 @@ M: Richard Weinberger <richard@nod.at>
>> M: Artem Bityutskiy <dedekind1@gmail.com>
>> M: Adrian Hunter <adrian.hunter@intel.com>
>> L: linux-mtd@lists.infradead.org
>> -T: git git://git.infradead.org/ubifs-2.6.git
>> +T: git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git
>
> Please keep the initial separate git
>
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs.git
Will fix.
Thanks,
//richard
prev parent reply other threads:[~2019-05-15 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 20:04 [PATCH] MAINTAINERS: Update UBI/UBIFS git tree location Richard Weinberger
2019-05-15 22:29 ` Joe Perches
2019-05-15 22:42 ` Richard Weinberger [this message]
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=494585403.60051.1557960134909.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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