linux-kernel - Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230417141706.GA493669@workstation>
Date:   Mon, 17 Apr 2023 23:17:06 +0900
From:   Takashi Sakamoto <o-takashi@...amocchi.jp>
To:     rdunlap@...radead.org
Cc:     Stefan Richter <stefanr@...6.in-berlin.de>,
        linux-kernel@...r.kernel.org,
        linux1394-devel@...ts.sourceforge.net, tiwai@...e.de,
        broonie@...nel.org
Subject: Re: [PATCH] MAINTAINERS: replace maintainer of FireWire subsystem

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