Jonathan Lebon 9410195760 tier-1: drop redundant tier-0 symlinks ... Instead of re-symlinking every tier-0 manifest, just include the tier-0 manifest directly. That way, rpm-ostree will already know to resolve its manifests within the tier-0 directory.		2024-09-16 09:18:05 -04:00
..
bootable-rpm-ostree.yaml	A few renames; oscore -> tier-1	2023-09-13 17:45:16 -04:00
bootc-generic-growpart	tier-1/gropwart: bail early on devicemapper targets	2024-08-09 16:50:14 -04:00
bootc-generic-growpart.service	Add bootc-generic-growpart	2024-05-01 10:31:12 -04:00
coreos-user-experience.yaml	ux: Drop runc	2024-05-20 15:49:39 -04:00
firmware.yaml	firmware: Include fwupd	2023-09-15 17:51:21 -04:00
fwupd.yaml	A few renames; oscore -> tier-1	2023-09-13 17:45:16 -04:00
generic-growfs.yaml	Add bootc-generic-growpart	2024-05-01 10:31:12 -04:00
initramfs-full.yaml	initramfs: Switch to `add_dracutmodules`	2024-08-22 09:38:07 -04:00
kernel.yaml	Introduce a tier-0 image	2023-09-15 15:11:01 -04:00
manifest.yaml	tier-1: drop redundant tier-0 symlinks	2024-09-16 09:18:05 -04:00
networking-tools.yaml	networking: Drop NetworkManager-team & teamd	2024-05-20 15:52:08 -04:00
persistent-journal.yaml	Mass rename tier-1/boot => bootc	2023-11-23 14:42:56 +02:00
podman.yaml	tier-1: Enable recommends, fix podman	2023-09-23 08:27:45 -04:00
system-configuration.yaml	system-config: Add crypto-policies-scripts	2024-08-13 10:33:31 -04:00