git-quiltimport

Apply a quilt patch series to Git

SYNOPSIS

] [-P|--prefix=] [--no-whitespace] [--whitespace=

-a, --all
    Apply all patches found in the patch directory.

-F, --force
    Force apply the patches, skipping checks that prevent applying potentially harmful patches.

-k, --keep-empty
    Keep empty commits after applying patches.

-m, --message=
    Use as the commit message for the patches.

-p, --patch-directory=

    Specify the directory containing the quilt patches.

-P, --prefix=
    Prepend to the commit message.

--no-whitespace
    Ignore whitespace differences when applying patches.

--whitespace=
    Handle whitespace differences according to

DESCRIPTION

git-quiltimport is a utility designed to apply a series of patches managed by the quilt patch management system into a Git repository. It parses the .quiltrc file to determine the patch directory and attempts to apply patches from that directory. The patches are applied in alphabetical order unless a series file is present in the patch directory, in which case the order specified in the file is used.

git-quiltimport aims to automate the application of quilt patches, simplifying the workflow for projects that utilize both Git and quilt. It is commonly used when integrating changes from external sources, such as vendor patches, that are managed as quilt patches.

This command provides options to control aspects of patch application, such as handling whitespace, specifying a prefix to prepend to the commit messages and adding a commit message to the patches. It also allows for appending an empty commit message to the patch.

<B>CONFIGURATION</B>

git-quiltimport reads configuration variables from .quiltrc, including the patch directory. Ensure that the .quiltrc file is correctly configured to point to the right patch location for proper execution.

HISTORY

git-quiltimport was created to facilitate the process of integrating patches managed by quilt into git repositories.
Its development has focused on providing a seamless bridge between these two systems, which are often used in conjunction for projects involving external patches or vendor updates.
The command has evolved to handle various patch formats and provide options for customizing the import process, catering to the specific needs of different projects and workflows.