Re: [Xen-devel] [RFC] Re-working the patch submission guide

[Lars Kurth <lars.kurth@xxxxxxxxxx>]

On 02/08/2019, 14:03, "Julien Grall" <julien.grall@xxxxxxx> wrote:

    
    
    On 02/08/2019 14:02, Julien Grall wrote:
    > Hi Jan,
    > 
    > On 02/08/2019 13:52, Jan Beulich wrote:
    >> On 02.08.2019 13:14, Lars Kurth wrote:
    >>>> 1.5.4 Sending Patches Manually
    >>> This should be removed or state NOT TO DO this
    >>
    >> Please don't. I'm not meaning to start using git for patch submission
    >> any time soon (if ever), and I don't see why this should be a
    >> requirement.
    > Well, someone using this is likely to mess it up. So I agree with Lars 
and this 
    > should at least disagree and discourage to use it.
    
    s/disagree/be removed/
    
OK. That seems to be agreed. The intention of removing it is to encourage 
newcomers to use the tools we have and which we know work.

Any other general feedback on how I am planning to approach this?

In essence, we will end up with 
* What's in a patch series/patch  - terminology and our expectations
   - Possibly with a link to some best practices and tools for planning for 
multiple versions (but should not be part of the doc itself)
   - Longer term it would be nice to get to something like: 
https://www.kernel.org/doc/html/v4.17/process/development-process.html - TBH I 
don't like the doc otself very much, but it has some good topics in it which we 
should cover
* The tooling mechanics for a single patch: set-up and steps using 
get_maintainers.pl 
* Follow-up: multiple versions, checking when stuff has gone in, ... 
* Specifics for QEMU, ...

Lars 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel