linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	 "brauner@kernel.org" <brauner@kernel.org>,
	"slava@dubeyko.com" <slava@dubeyko.com>
Subject: Re: HFS/HFS+ maintainership action items
Date: Tue, 22 Apr 2025 23:48:46 +0200	[thread overview]
Message-ID: <7f81ec6af1c0f89596713e144abd89d486d9d986.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <d4e0f37aa8d4daf83aa2eb352415cf110c846101.camel@physik.fu-berlin.de>

Hi Slava,

On Tue, 2025-04-22 at 23:47 +0200, John Paul Adrian Glaubitz wrote:
> Reducing the discussion on the repository for now.
> 
> To get a repository on git.kernel.org, you need to have an entry in MAINTAINERS.
> Thus, first we would need to get ourselves added to MAINTAINERS for the hfs code.
> 
> I have already an entry there as I'm maintaining arch/sh.
> 
> You can just send a patch to the LKML, get me and you added to MAINTAINERS, see
> [1] and [2] for an example how to do that. Once Linus has merged your patch, you
> can request a kernel.org and git tree here [3].
> 
> Adrian
> 
> > [1] https://lore.kernel.org/lkml/87v8k7rrnf.wl-ysato@users.sourceforge.jp/T/
> > [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/MAINTAINERS?id=80510b63f7b6bdd30e07b3a42115d0a324e20cd6
> > [3] https://korg.docs.kernel.org/accounts.html

Please see also: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/MAINTAINERS?id=bf8f5de17442bba5f811e7e724980730e079ee11

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2025-04-22 21:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21 21:52 HFS/HFS+ maintainership action items Viacheslav Dubeyko
2025-04-22  2:43 ` Theodore Ts'o
2025-04-22  4:16   ` Darrick J. Wong
2025-04-22  7:21     ` John Paul Adrian Glaubitz
2025-04-22  7:20   ` John Paul Adrian Glaubitz
2025-04-22 12:35 ` John Paul Adrian Glaubitz
2025-04-22 21:12   ` Viacheslav Dubeyko
2025-04-22 21:47     ` John Paul Adrian Glaubitz
2025-04-22 21:48       ` John Paul Adrian Glaubitz [this message]
2025-04-25  1:06         ` Viacheslav Dubeyko
2025-04-25 10:17           ` 回复: " 李扬韬
2025-04-25 11:32             ` John Paul Adrian Glaubitz
2025-04-25 11:39               ` 回复: " 李扬韬
2025-04-25 18:25                 ` Viacheslav Dubeyko
2025-04-25 19:36                   ` 回复: " 李扬韬
2025-04-25 19:44                     ` Viacheslav Dubeyko
2025-04-26  6:17                       ` 回复: " 李扬韬
2025-04-26  6:59                         ` John Paul Adrian Glaubitz
2025-04-27 20:28                         ` Viacheslav Dubeyko
2025-05-02  3:01                           ` Theodore Ts'o
2025-05-02 19:14                             ` Viacheslav Dubeyko
2025-05-03  5:39                               ` Theodore Ts'o
2025-05-05 23:08                                 ` Viacheslav Dubeyko
2025-04-25 20:51                     ` John Paul Adrian Glaubitz
2025-04-25 18:02             ` Viacheslav Dubeyko

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=7f81ec6af1c0f89596713e144abd89d486d9d986.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=Slava.Dubeyko@ibm.com \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=slava@dubeyko.com \
    /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;
as well as URLs for NNTP newsgroup(s).