From: Patrick Steinhardt <ps@pks.im>
To: Phillip Wood via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH] docs: add BreakingChanges to TECH_DOCS target
Date: Wed, 19 Mar 2025 10:33:27 +0100 [thread overview]
Message-ID: <Z9qPZ_7VVV6L95WE@pks.im> (raw)
In-Reply-To: <pull.1921.git.git.1742308900290.gitgitgadget@gmail.com>
On Tue, Mar 18, 2025 at 02:41:40PM +0000, Phillip Wood via GitGitGadget wrote:
> From: Phillip Wood <phillip.wood@dunelm.org.uk>
>
> When BreakingChanges.txt was added in 57ec9254eb9 (docs: introduce
> document to announce breaking changes, 2024-06-14) there was no
> corresponding change to the Makefile to build it. Fix that by adding it
> to the TECH_DOCS target.
Makes sense, thanks for this improvement!
Patrick
prev parent reply other threads:[~2025-03-19 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 14:41 [PATCH] docs: add BreakingChanges to TECH_DOCS target Phillip Wood via GitGitGadget
2025-03-19 9:33 ` Patrick Steinhardt [this message]
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=Z9qPZ_7VVV6L95WE@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).