Progress:
TIER 2 · MODULE 36· Intermediate

git quiltimport

Old kernel/userspace workflow ingestion.

🎯 What & why

Import a Quilt patch series into Git history, one commit per patch. Old kernel and userspace projects ship code this way and this is the clean ingestion path.

🧠 Mental model

Read the series file, apply each listed patch in order, and create one Git commit per patch with the patch headers as the commit message. A scripted replay of quilt push.

🛠️ Synopsis

git quiltimport [--author <author>] [--patches <dir>]
                [--series <file>] [--keep-non-patch]

Run inside an existing Git repo. Defaults: --patches patches/ and
--series patches/series. Each non-comment line in the series file
names a patch file relative to the patches dir; each is applied and
committed in order.

🎚️ Switches & options

FlagWhat it does
--author <author>Override the author when a patch lacks a From: header. Format: 'Name <email>'.
--patches <dir>Directory holding the patch files; defaults to patches/ under the current dir.
--series <file>Path to the series file; defaults to <patches-dir>/series.
--keep-non-patchKeep the [PATCH] prefix and similar bracket tags in the imported commit subject.
--dry-runWalk the series file and validate without creating any commits.

💡 Use cases

🧪 Examples

Import the default patches/ + patches/series
git quiltimport
Import from a debian-style layout
git quiltimport --patches debian/patches --series debian/patches/series
Supply a fallback author for header-less patches
git quiltimport --author 'Alice <alice@127.0.0.1>'
Dry-run to validate the series first
git quiltimport --dry-run

🎓 Recommendations

🪤 Common pitfalls

🔗 Related modules

📝 Quiz

Hit each option, then Check answers. Score is recorded; Next is always open.