From: Alyssa Ross <hi@alyssa.is>
To: Demi Marie Obenour <demiobenour@gmail.com>,
Spectrum OS Development <devel@spectrum-os.org>
Subject: Re: Generating file lists from a script
Date: Sun, 31 Aug 2025 12:51:19 +0200 [thread overview]
Message-ID: <875xe3zrvc.fsf@alyssa.is> (raw)
In-Reply-To: <03036e25-a278-4f3c-870f-f03fb4d546ca@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Demi Marie Obenour <demiobenour@gmail.com> writes:
> Maintaining the lists of files and directories in the makefiles
> is error-prone. Would it make sense to use a script to generate
> them from the git repository? The script would get it right
> every time, whereas I tend to get it wrong more times than not.
As long as we're still maintaining a list of files in the source tree,
rather than doing something like copying whole directories, and we don't
have to make the Makefiles less readable to accomodate the script, I
don't mind.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2025-08-31 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 2:59 Generating file lists from a script Demi Marie Obenour
2025-08-31 10:51 ` Alyssa Ross [this message]
2025-09-01 22:14 ` Demi Marie Obenour
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=875xe3zrvc.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).