On 14/10/21 03.30, Junio C Hamano wrote:
Side note. We want a new feature to be built on 'master' (or
the last feature release, if nothing in flight conflicts
with it)), and a bugfix to be built on one of the older
release point (to be applicable to the maintenance tracks).
But the section we are discussing, i.e. how to run
format-patch, is not the place to do so, as it is too
late---it must be decided before the contributor starts
working on the series. As the example of this document is
about adding a new "feature", we should have a sentence to
explain, in the "Set up your workspace" section, why we
chose 'master' as the base point (and the existing text
already says why).
It has been described before:
Let's start by making a development branch to work on our changes. Per
`Documentation/SubmittingPatches`, since a brand new command is a new feature,
it's fine to base your work on `master`. However, in the future for bugfixes,
etc., you should check that document and base it on the appropriate branch.
Leave it as is?
--
An old man doll... just what I always wanted! - Clara