Package: devscripts Version: 2.10.55 Severity: wishlist Tags: patch Hi, at the moment, I think that the diff2patches manpage is unclear in two ways. First, it doesn't specify that if debian/patches/ doesn't exist, then the patches are put straight in the debian/ directory. Second, it doesn't provide any information about the naming conventions for the broken-out patches that it produces.
I've written a proposed patch that adds more information to the manpage. Regards, Daniel
Index: scripts/diff2patches.1 =================================================================== --- scripts/diff2patches.1 (revision 2015) +++ scripts/diff2patches.1 (working copy) @@ -21,6 +21,9 @@ .TP \fB\-\-version\fR Output version information and exit. +.SH "PATCH NAME CONVENTIONS" +.LP +For each file outside the debian/ directory that is modified in the .diff.gz, one patch is created. The name of the patch is the relative path from the base of the source tree to the modified file, with three underscores substituted for each backslash. The new patch names end in '.patch'. .SH "FILES" .LP \fIdebian/control\fP @@ -28,7 +31,7 @@ .br \fIdebian/patches\fP When present and is a directory, patches are extracted in that directory, -unless \fIDEB_PATCHES\fP is defined (read the "ENVIRONMENT VARIABLES" section below). +unless \fIDEB_PATCHES\fP is defined (read the "ENVIRONMENT VARIABLES" section below). If \fIdebian/patches\fP doesn't exist, and \fIDEB_PATCHES\fP isn't set, then patches are extracted into the \fIdebian\fP directory. .SH "ENVIRONMENT VARIABLES" .TP \fIDEB_PATCHES\fP
signature.asc
Description: OpenPGP digital signature
