From: Eric Biggers <ebiggers@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-doc@vger.kernel.org, workflows@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH] docs: submitting-patches: Require base tree information
Date: Tue, 20 Oct 2026 23:39:27 -0700 [thread overview]
Message-ID: <20261021063927.GA31908@sol> (raw)
In-Reply-To: <363b228a-7e96-481a-b70f-195ba55d025e@kernel.org>
On Wed, Oct 21, 2026 at 08:26:28AM +0200, Krzysztof Kozlowski wrote:
> On 20/10/2026 23:22, Eric Biggers wrote:
> > -Make sure that base commit is in an official maintainer/mainline tree
> > -and not in some internal, accessible only to you tree - otherwise it
> > -would be worthless.
> > + If ``git format-patch`` with ``--base=auto`` (or
> > + ``format.useAutoBase=true``) can't detect a base commit, e.g. due to
> > + the current branch having no upstream tracking branch, it exits with
> > + an error. In such cases, pass an explicit base commit to ``--base``
> > + instead. This is also needed if git detects the wrong base commit,
> > + such as when the upstream branch has local, unpublished commits.
> > +
> > +The base commit must be in a well-known public tree, such as the
> > +subsystem development branch the patch is targeting. See
> > +:ref:`obtain_a_current_source_tree`. Mainline or the latest linux-next
> > +can also be acceptable bases, depending on the subsystem.
>
> I disagree, that's pointlessly too hard requirement.
>
> For many of my contributions base is obvious and not needed to be
> explicitly defined. For all the patches I accept, answer is the same -
> base is either obvious or if not and patch does not apply, then the base
> does not matter.
>
> Requiring it is just bureaucracy without actual benefit.
>
> The only benefit would be if maintainer COULD change its base to apply
> some patch with odd base... but this cannot happen. Maintainer base is
> fixed - it's the HEAD of his development branch for given category of
> commits (e.g. DTS branch for SoC maintainers).
There are many use cases for applying patches besides the final patch
acceptance, such as review (by anyone, not just a maintainer), testing,
CI systems, etc.
HEAD of a branch is of course not fixed, and changes every time a patch
gets applied. That's especially relevant when wanting to check out an
old patch for any reason. Trying to guess a base commit based on the
date and patch subject is a waste of time.
- Eric
next prev parent reply other threads:[~2026-10-21 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 21:22 [PATCH] docs: submitting-patches: Require base tree information Eric Biggers
2026-10-20 22:07 ` Konstantin Ryabitsev
2026-10-21 6:07 ` Randy Dunlap
2026-10-21 6:35 ` Krzysztof Kozlowski
2026-10-21 6:44 ` Eric Biggers
2026-10-21 6:47 ` Krzysztof Kozlowski
2026-10-21 3:17 ` Weijie Yuan
2026-10-21 6:26 ` Krzysztof Kozlowski
2026-10-21 6:39 ` Eric Biggers [this message]
2026-10-21 6:41 ` Krzysztof Kozlowski
2026-10-21 6:49 ` Eric Biggers
2026-10-21 11:55 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261021063927.GA31908@sol \
--to=ebiggers@kernel.org \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.