public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: rdunlap@infradead.org
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	linux-kernel@vger.kernel.org,
	linux1394-devel@lists.sourceforge.net, tiwai@suse.de,
	broonie@kernel.org
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem
Date: Mon, 17 Apr 2023 23:17:06 +0900	[thread overview]
Message-ID: <20230417141706.GA493669@workstation> (raw)
In-Reply-To: <20230312070728.GA421475@workstation>

Hi Randy,

I'm sorry that I didn't notice your reply, but I'm off from the receivers
list of the message.

> Hi--
> 
>On 3/11/23 23:07, Takashi Sakamoto wrote:
>> Hi,
>> 
>>>
>>> It's good to see you being active in the kernel and related userland
>>> development/ maintainership, and that you have a plan for the next years.
>> 
>> At the moment, I have a problem about the list archive.
> 
> If there is still a problem about the mailing list archives,
> Hank Leininger at marc.info has been pretty good in the past about providing
> archives fore lore.kernel.org.
> See the bottom of https://marc.info/?q=about for his email address.
 
Thanks for the information. As a quick glimpse, linux1394-devel has been
archived since 2003. It looks to be a good source to push into
lore.kernel.org, while I know that the list archive should include many
spams since any one is allowed to post to the list without subscribing and
being moderated at one time. It is one of my reason not to use the list
so actively. I need to make filter to remove them before pushing.
Furthermore, the ownership of list is still unclear to me. I have a small
hesitation to use it further...
 
> Are you waiting for the kernel.org account before merging the update to the
> MAINTAINER's file?

I've already got the account and enough permission to linux1394
repository, but The repository is inactive so long, and abandoned. Looking
ahead to my future work, I'm preparing them at present.


Thanks

Takashi Sakamoto

  parent reply	other threads:[~2023-04-17 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06  3:58 [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem Takashi Sakamoto
2023-03-06 22:17 ` Randy Dunlap
2023-03-09 14:14 ` Takashi Iwai
2023-03-10 20:03 ` Stefan Richter
2023-03-11  8:03   ` Takashi Sakamoto
2023-03-11  9:15     ` Stefan Richter
2023-03-12  7:07       ` Takashi Sakamoto
2023-04-09 23:56         ` Randy Dunlap
2023-04-17 14:17         ` Takashi Sakamoto [this message]
2023-04-20 16:02 ` Takashi Sakamoto

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=20230417141706.GA493669@workstation \
    --to=o-takashi@sakamocchi.jp \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=rdunlap@infradead.org \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=tiwai@suse.de \
    /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