Ease your vendor branch management worries with Piston, a tool to copy vendor / upstream code to your own repository, while preserving your local patches.
Upgrade Subcommand Documentation
When to use it
Use the upgrade command to upgrade one or more directories from the Piston v1.x Subversion properties to the new YAML file format. This will not update any of your Pistonized folders.
In the Piston v1.x-era, Piston was a Subversion-centric tool. Piston stored it's meta-data in Subversion properties. Now that Piston is able to use Subversion or Git working copies, the metadata had to be stored in a backend-agnostic manner. The easiest and fastest way was to use files. Each Pistonized folder has an extra file named .piston.yml at the root. This file contains metadata about the repository, working copy and when last update from the upstream repository was made.
If you have already converted to using something else than Subversion, you are on your own. The YAML file is pretty self-explanatory, and you can create it yourself.
Command summary
SYNOPSIS
piston upgrade [directories*] [options]+
PARAMETERS
directories (-1 ~> directories=.)
Which directory/directories to convert from Piston 1.x to Piston 2.x.
Not specifying this argument recursively converts the whole directory
tree starting from the current dir.
--verbose=[verbose], -v (0 ~> integer(verbose=0))
Verbosity level (0 to 5, 0 being the default)
--quiet, -q
--force
--dry-run
--help, -h
