New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
fcm-branch-create.pod in vendors/lib/FCM/CLI – NEMO

source: vendors/lib/FCM/CLI/fcm-branch-create.pod @ 10669

Last change on this file since 10669 was 10669, checked in by nicolasmartin, 5 years ago

Import latest FCM release from Github into the repository for testing

File size: 2.8 KB
Line 
1=head1 NAME
2
3fcm branch-create (bcreate, bc)
4
5=head1 SYNOPSIS
6
7Creates a branch.
8
9    fcm branch-create [OPTIONS] NAME [SOURCE]
10
11=head1 ARGUMENTS
12
13NAME is a short name for the branch, which should contain only characters in the
14set [A-Za-z0-9_\-\.]. If the --ticket=N option is not specified and NAME
15contains only a list of positive integers separated by [_-] (an underscore or a
16hyphen), the command will assume that NAME also specifies the related ticket
17numbers.
18
19SOURCE can be an URL or a Subversion working copy. Otherwise, the current
20working directory must be a working copy. The specified URL (or the URL of the
21working copy) must be URL under a standard FCM project.
22
23=head1 OPTIONS
24
25=over 4
26
27=item --branch-of-branch, --bob
28
29If this option is specified and the SOURCE is a branch, it will create a new
30branch from the SOURCE branch. Otherwise, the branch is created from the trunk.
31
32=item --non-interactive
33
34Do no interactive prompting. This option implies --svn-non-interactive.
35
36=item --password=PASSWORD
37
38Specify a password for write access to the repository.
39
40=item --rev-flag=NONE|NORMAL|NUMBER
41
42Specify a flag for determining the prefix of the branch name. The flag can be
43the string "NORMAL", "NUMBER" or "NONE".  "NORMAL" is the default behaviour,
44in which the branch name will be prefixed with a Subversion revision number if
45the revision is not associated with a registered FCM revision keyword. If the
46revision is registered with a FCM revision keyword, the keyword will be used in
47place of the number. If "NUMBER" is specified, the branch name will always be
48prefixed with a Subversion revision number. If "NONE" is specified, the branch
49name will not be prefixed by a revision number or keyword.
50
51=item --svn-non-interactive
52
53Do no interactive prompting at commit time. This option is implied by
54--non-interactive.
55
56=item --switch
57
58C<fcm switch> the current working directory (if it contains a relevant working
59copy) to point to the newly created branch after the branch is created.
60
61=item --ticket=N, -k N
62
63Specify one (or more) Trac ticket. If specified, the ticket numbers will be
64included in the commit log message. Multiple tickets can be set by specifying
65this option multiple times, or by specifying the tickets in a comma-separated
66list.
67
68=item --type=TYPE, -t TYPE
69
70Specify the type of the branch to be created. It must be one of the following:
71
72 DEV::USER [DEV, USER] - a development branch for the user
73 DEV::SHARE [SHARE]    - a shared development branch
74 TEST::USER [TEST]     - a test branch for the user
75 TEST::SHARE           - a shared test branch
76 PKG::USER [PKG]       - a package branch for the user
77 PKG::SHARE            - a shared package branch
78 PKG::CONFIG [CONFIG]  - a configuration branch
79 PKG::REL [REL]        - a release branch
80
81If not specified, the default is to create a development branch for the current
82user, i.e.  DEV::USER.
83
84=back
85
86=cut
Note: See TracBrowser for help on using the repository browser.