Guidelines for Submitting an RFC PATCH

Guidelines for Submitting an RFC PATCH

[Joe Smith]

Hi All,

What are the guidelines for submitting an RFC patch? If a developer
wants to get early input on a design is it fine to submit a patch that
is in reasonable shape but does not fully meets the requirements of a
regular patch, for example, the patch consists of a series of patches,
it only compiles when all patches in the series are applied. Going
through the process of meeting all the patch requirements for an RFC
patch seems too much.

Regards


-- 
JS

Re: Guidelines for Submitting an RFC PATCH

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 854 bytes --]

On Mon 2018-03-12 16:01:08, Joe Smith wrote:
> Hi All,
> 
> What are the guidelines for submitting an RFC patch? If a developer
> wants to get early input on a design is it fine to submit a patch that
> is in reasonable shape but does not fully meets the requirements of a
> regular patch, for example, the patch consists of a series of patches,
> it only compiles when all patches in the series are applied. Going
> through the process of meeting all the patch requirements for an RFC
> patch seems too much.

There are not many guidelines for that. Just mark it RFC :-).

Series that only compiles when full would be fine for example. (But
you may get complains from 0 day testing bots, not sure).
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]