Browsing Occitan (post 1500) translation

36.

More recent patches modify files in patch %s\n

38.

Edit the specified file(s) in \$EDITOR (%s) after adding it (them) to
the topmost patch.

40.

Print the list of files that the topmost or specified patch changes.

-a[tab]List all files in all applied patches.

-l[tab]Add patch name to output.

-v[tab]Verbose, more user friendly output.

--combine patch
[tab]Create a listing for all patches between this patch and
[tab]the topmost applied patch. A patch name of \"-\" is equivalent
[tab]to specifying the first applied patch.

43.

Integrate the patch read from standard input into the topmost patch:
After making sure that all files modified are part of the topmost
patch, the patch is applied with the specified strip level (which
defaults to 1).

-p strip-level
[tab]The number of pathname components to strip from file names
[tab]when applying patchfile.

46.

Fork the topmost patch. Forking a patch means creating a verbatim copy
of it under a new name, and use that new name instead of the original
one in the current series. This is useful when a patch has to be
modified, but the original version of it should be preserved, e.g.
because it is used in another series, or for the history. A typical
sequence of commands would be: fork, edit, refresh.

If new_name is missing, the name of the forked patch will be the current
patch name, followed by \"-2\". If the patch name already ends in a
dash-and-number, the number is further incremented (e.g., patch.diff,
patch-2.diff, patch-3.diff).

47.

Patch %s exists already, please choose a new name\n

49.

Fork of patch %s created as %s\n

51.

Generate a dot(1) directed graph showing the dependencies between
applied patches. A patch depends on another patch if both touch the same
file or, with the --lines option, if their modifications overlap. Unless
otherwise specified, the graph includes all patches that the topmost
patch depends on.
When a patch name is specified, instead of the topmost patch, create a
graph for the specified patch. The graph will include all other patches
that this patch depends on, as well as all patches that depend on this
patch.

--all[tab]Generate a graph including all applied patches and their
[tab]dependencies. (Unapplied patches are not included.)

--reduce
[tab]Eliminate transitive edges from the graph.

--lines[=num]
[tab]Compute dependencies by looking at the lines the patches modify.
[tab]Unless a different num is specified, two lines of context are
[tab]included.

--edge-labels=files
[tab]Label graph edges with the file names that the adjacent patches
[tab]modify.

-T ps[tab]Directly produce a PostScript output file.

53.

Grep through the source files, recursively, skipping patches and quilt
meta-information. If no filename argument is given, the whole source
tree is searched. Please see the grep(1) manual page for options.

-h[tab]Print this help. The grep -h option can be passed after a
[tab]double-dash (--). Search expressions that start with a dash
[tab]can be passed after a second double-dash (-- --).

55.

Print or change the header of the topmost or specified patch.

-a, -r, -e
[tab]Append to (-a) or replace (-r) the exiting patch header, or
[tab]edit (-e) the header in \$EDITOR (%s). If none of these options is
[tab]given, print the patch header.
[tab]
--strip-diffstat
[tab]Strip diffstat output from the header.

--strip-trailing-whitespace
[tab]Strip trailing whitespace at the end of lines of the header.

--backup
[tab]Create a backup copy of the old version of a patch as patch~.