Re: [PATCH 0/3] Towards a re-organized submitting patches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03.03.24 17:31, Jonathan Corbet wrote:
> Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx> writes:
>> I wanted to clean up the development-process documentation. There is
>> however no easy way to break the ice here:
>>
>> The elephant in the room is that there is some unclear relation between
>> 5.Posting.rst, 6.Followthrough.rst and submitting-patches.rst.
>> (Yes, I know each document has its own history...; but let us put the
>> history aside for now.)
> 
> FWIW, the objective of those two documents is quite different; one is a
> high-level overview of how the development process as a whole works, the
> other is a detailed guide to submitting work for consideration.

Sorry, I'm slightly confused here, so I have to ask: which is which?

Due to the "*essential*" in the headline of submitting-patches.rst and
its "For *detailed* information on how the kernel development process
works, see Documentation/process/development-process.rst" in the intro
make it sounds to me like submitting-patches.rst should be the one with
the high-level overview. But...

> Again, let's remember the different purposes of these documents.  The
> development-process document is an overall description of the process,
> so it doesn't need the details.

...this makes it sounds like you consider it the other way around. And
for me that feels the wrong, as why describe the overall process in
detail, but leave the most important part of the process to some other
document?

/me wonders what he is missing

Ciao, Thorsten








[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux