Accept change sets into a repository workspace and optionally
load them into the local workspace.
Purpose
The scm accept subcommand
accepts change sets into a repository workspace. If you run it in
a local workspace, the accepted change sets are also loaded into the
local workspace.
Synopsis
- To run scm accept after you have used scm login to
create stored credentials:
scm accept [ -r
| --repository-uri ] repository URI or nickname [ -d | --dir ] workspace-path { [ [ -q | --quiet ] | [ -v | --verbose ] ] [ -s | --source ] source workspace or stream [ -t | --target ] target workspace or stream [ -i | --in-place-markers ] change set ... }
- To run scm accept supplying credentials
on the command line:
scm accept [ -r | --repository-uri ] repository URI [ -u | --username ] user ID in repository [ -P | --password ] password for user ID in repository
[ -d | --dir ] workspace-path { [ [ -q | --quiet ] | [ -v | --verbose ] ] [ -s | --source ] source workspace or stream [ -t | --target ] target workspace or stream [ -i | --in-place-markers ] change set ... }
Options and arguments
- [ -b
| --baseline ]
- Indicates the given baseline should
be accepted (alias, UUID, or name).
- [ -c
| --changes ]
- Indicates that only the specified change
sets should be accepted (alias, UUID, or name).
- [ -C
| --components ]
- Indicates that all changes in the
given components should be accepted (alias, UUID, or name).
- [ -d | --dir ] workspace-path
- The path name of a local workspace created
by scm load or scm share.
This subcommand runs with workspace-path set as
the current working directory. You can omit this option if the current
working directory is in a local workspace.
- [ --flow-components ]
- Accept component additions and deletions.
- [ --no-merge ]
- Disable automatic merging of conflicts.
- [ -P | --password ] password for user ID in repository
- The password for the specified user ID in
the named repository. If this option is not included on the command
line, you are prompted for a password. If you specified a repository
URI or nickname for which you have stored credentials using the scm
login command, this option is ignored.
- [ -q | --quiet ]
- Suppress most informational messages while
operating.
- [ -r | --repository-uri ] repository URI
- Specifies the repository in which to take
this action. If you have stored repository credentials using the scm
login command, you can use the nickname you supplied for
these stored credentials
- [ -t | --target ] target
workspace or stream
- The name, alias, or UUID of the target workspace or stream.
- [ -u | --username ] user ID in repository
- Specifies a user ID that exists in the named
repository. If you specified a repository URI or nickname for which
you have stored credentials using the scm login command,
this option is ignored.
- [ -v | --verbose ]
- Provide additional informational messages
while operating.
- change set ...
- A space-separated list of one or more change sets to accept. Specify
change sets by name, alias, or UUID. If omitted, all incoming change
sets for the workspace are accepted.
Examples
Working in a local workspace,
scm status output
indicates an incoming change set.
C:\local-workspaces\HelloJazz>scm status
Workspace: (1101) "HelloJazz" <-> (1102) "HelloJazz Stream"
Component: (1103) "HelloJazz"
Baseline: (1104) 2 "base"
Incoming:
Change sets:
(1106) --$ 57286 "bogus repository error when accepting team invitation>
Run
scm accept to
accept the change set into the repository workspace and load it into
the local workspace.
C:\local-workspaces\HelloJazz>scm accept 1106
Accepting changes from "HelloJazz Stream" into "HelloJazz"
No baselines to flow.
Downloading files...
Downloading /com.example.hellojazz.rcp.ui/src/com/example/hellojazz/rcp/ui/actions/HelloJazzAction.java (3.4 KB)
Download complete.
Change sets
Component "HelloJazz"
(1106)
--m- /com.example.hellojazz.rcp.ui/src/com/example/hellojazz/rcp/ui/actions/HelloJazzAction.java
Conflicts
The
scm accept output
shows the file that the change set modified and indicates that there
are no conflicts.