From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>,
Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: Best practices for submitting tree-wide changes
Date: Sat, 01 Nov 2025 13:22:50 +0100 [thread overview]
Message-ID: <875xbuq6w5.fsf@alyssa.is> (raw)
In-Reply-To: <c16dcffe-f02f-4a78-8277-48ae932403d5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
Demi Marie Obenour <demiobenour@gmail.com> writes:
> In some cases, the same change should be made to many parts of
> the codebase. This includes things like adding set -o pipefail to
> shell scripts or moving command substitutions to their own commands.
> Should one send a single patch that makes all the changes, or should
> one send a bunch of tiny patches?
>
> Preferably, the answer should be added to the documentation so people
> don't need to ask again :)
A single patch with no component prefix in the subject line is fine.
Documentation doesn't currently have a good place for this sort of thing
but I'll note the request for when we restructure it next year.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2025-11-01 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 21:11 Best practices for submitting tree-wide changes Demi Marie Obenour
2025-11-01 12:22 ` Alyssa Ross [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=875xbuq6w5.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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).