source: LMDZ6/branches/Amaury_dev/tools/fcm/lib/FCM/CLI/fcm-mkpatch.pod @ 5095

Last change on this file since 5095 was 5095, checked in by abarral, 4 months ago

Revert cosp*/ from the trunk, as it's external code
Add missing bits from FCM2 source

File size: 2.1 KB
Line 
1=head1 NAME
2
3fcm mkpatch
4
5=head1 SYNOPSIS
6
7Create patches from specified revisions of a URL
8
9    fcm mkpatch [OPTIONS] URL [OUTDIR]
10
11=head1 ARGUMENTS
12
13If OUTDIR is specified, the output is sent to OUTDIR. Otherwise, the output will
14be sent to a default location in the current directory ($PWD/fcm-mkpatch-out).
15The output directory will contain the patch for each revision as well as a
16script for importing the patch.
17
18A warning is given if the URL is not of a branch in a FCM project or if it is a
19sub-directory of a branch.
20
21=head1 OPTIONS
22
23=over 4
24
25=item --exclude arg
26
27Exclude a path in the URL. Multiple paths can be specified by using a
28colon-separated list of paths, or by specifying this option multiple times.
29
30The specified path must be a relative path of the URL. Glob patterns such as *
31and ? are acceptable. Changes in an excluded path will not be considered in the
32patch. A changeset containing changes only in the excluded path will not be
33considered at all.
34
35=item --organisation arg
36
37This option can be used to specify the name of your organisation.
38
39The command will attempt to parse the commit log message for each revision in
40the patch. It will remove all merge templates, replace Trac links with a
41modified string, and add information about the original changeset. If you
42specify the name of your organisation, it will replace Trac links such as
43"ticket:123" with "$organisation_ticket:123", and report the original changeset
44with a message such as "$organisation_changeset:1000".  If the organisation
45name is not specified then it defaults to "original".
46
47=item --revision=arg, -r arg
48
49Specify a revision number or a revision number range.
50
51If a revision is specified with the --revision option, it will attempt to create
52a patch based on the changes at that revision. If a revision is not specified,
53it will attempt to create a patch based on the changes at the HEAD revision. If
54a revision range is specified, it will attempt to create a patch for each
55revision in that range (including the change in the lower range) where changes
56have taken place in the URL. No output will be written if there is no change in
57the given revision (range).
58
59=back
60
61=cut
Note: See TracBrowser for help on using the repository browser.