EDIT-PATCH(1)

✨ EDIT-PATCH(1) β€” General Commands Manual πŸ’–

🌸 NAME

bestie, okay so this one is edit-patch and add-patch πŸ¦‹ β€” tools for preparing patches for Debian source packages. literally the cutest little duo πŸŽ€

🧚 SYNOPSIS

edit-patch path/to/patch

add-patch path/to/patch

πŸ’… DESCRIPTION

okay so edit-patch is a wrapper script around the Quilt, CDBS, and dpatch patch systems πŸ”₯. it's giving "I'll handle the messy stuff so you don't have to." it simplifies preparing and editing patches to Debian source packages, and you don't have to care which patch system is in use. ngl that's so iconic πŸ‘‘. run it from inside the root directory of the source package, and it can edit existing patches sitting in debian/patches ✨.

it can also incorporate brand-new patches πŸ’œ. if you point it at a patch that isn't already there, it copies the patch into debian/patches in the correct format for whatever patch system is in use. then the patch gets applied and a subshell pops open so you can edit it 🫢. typing exit or pressing Ctrl-d closes the subshell and launches an editor so you can record the debian/changelog entry πŸ“.

edit-patch is integrated with the Bazaar and Git version control systems 🌈. the patch gets automatically added to the tree, and the debian/changelog entry becomes the commit message. main character energy, fr fr 😭.

if no patch system is present, the patch is applied inline, and a copy is stored in debian/patches-applied. πŸ’€

add-patch is the non-interactive version of edit-patch πŸ™ˆ. the patch still gets incorporated, but no editor or subshell spawns. quick and clean ⭐.

πŸŽ€ AUTHORS

edit-patch was written by Daniel Holbach <daniel.holbach@canonical.com>, Michael Vogt <michael.vogt@canonical.com>, and David Futcher <bobbo@ubuntu.com> πŸ“.

This manual page was written by Andrew Starr-Bochicchio <a.starr.b@gmail.com> 🫢.

Both are released under the terms of the GNU General Public License, version 3 🌸.


bye bestie, that's the whole tea β˜• β€” Debian Utilities, EDIT-PATCH(1) πŸ’–βœ¨

πŸ“¦ where this page comes from