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] [day] [month] [year] [list]
Message-ID: <c17cd9f3-0651-49ce-805f-d94ef2b232c1@vivo.com>
Date: Wed, 6 Aug 2025 00:43:49 +0800
From: Yangtao Li <frank.li@...o.com>
To: Viacheslav Dubeyko <Slava.Dubeyko@....com>,
 "glaubitz@...sik.fu-berlin.de" <glaubitz@...sik.fu-berlin.de>,
 "slava@...eyko.com" <slava@...eyko.com>
Cc: "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: update location of hfs&hfsplus trees

Hi Slava,

在 7/30/2025 3:12 AM, Viacheslav Dubeyko 写道:
> On Tue, 2025-07-29 at 10:01 -0600, Yangtao Li wrote:
>> Update it at MAINTAINERS file.
>>
>> Signed-off-by: Yangtao Li <frank.li@...o.com>
>> ---
>>   MAINTAINERS | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 7a4e63bacaa4..48b25f1e2c01 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -10659,6 +10659,7 @@ M:	John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
>>   M:	Yangtao Li <frank.li@...o.com>
>>   L:	linux-fsdevel@...r.kernel.org
>>   S:	Maintained
>> +T:	git git://git.kernel.org/pub/scm/linux/kernel/git/vdubeyko/hfs.git
>>   F:	Documentation/filesystems/hfs.rst
>>   F:	fs/hfs/
>>   
>> @@ -10668,6 +10669,7 @@ M:	John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
>>   M:	Yangtao Li <frank.li@...o.com>
>>   L:	linux-fsdevel@...r.kernel.org
>>   S:	Maintained
>> +T:	git git://git.kernel.org/pub/scm/linux/kernel/git/vdubeyko/hfs.git
>>   F:	Documentation/filesystems/hfsplus.rst
>>   F:	fs/hfsplus/
>>   
> Makes sense. We need to update it here.
>
> By the way, we have also [1]. I am collecting patches there at first too and we
> can use it for the initial testing. Also, we have very simple bug tracking
> system [2] and I am tracking the known and opened issues there. Should we add
> this information too?
>
> We have empty WiKi there, but we could add the information there too.


Do you mind we add those facility step by step, or add those facility in 
one patch?


Thx,

Yangtao


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ