linux-kernel - Re: [PATCH] Remove me from maintainers for serial and mmc

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: <452D34DC.2060704@drzeus.cx>
Date:	Wed, 11 Oct 2006 20:15:56 +0200
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Andrew Morton <akpm@...l.org>
CC:	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>
Subject: Re: [PATCH] Remove me from maintainers for serial and mmc

Andrew Morton wrote:
> Thanks.  Please send a MAINTAINERS patch.
>   

Some practical questions for my new role. I intend to set up a public
git repository (preferably on kernel.org, but I don't currently know the
criteria there) as a means to expose my patches.

>From what I've observed, the work flow is something like this:

Have a "for-andrew" and a "for-linus" branch, depending on stuff for -mm
or the main tree. Moving stuff between the two will be done in my rep
and after which I send pull requests to LKML.

This might be a misunderstanding on my part, or for other reasons, not a
way you wish to work. So I'm open to input on how I should structure things.

Rgds
Pierre

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/