Skip to content
/ tclap Public

WARNING: This is NOT the official upstream tclap git repository

Notifications You must be signed in to change notification settings

Slicer/tclap

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 

Repository files navigation

What is this project ?

This project is NOT the official tclap repository.

It is a fork of tclap sources hosted at https://sourceforge.net/p/tclap/code.

It is used as staging area to maintain and test patches that will be contributed back to the official repository.

What is the branch naming convention ?

Each branch is named following the pattern slicer-YYYY-MM-DD-vY.Y.Z-SHA{N}

where:

  • vX.Y.Z is the version of the forked project
  • YYYY-MM-DD is the date of the last official commit associated with the branch.
  • SHA{N} are the first N characters of the last official commit associated with the branch.

For more details, see https://www.slicer.org/wiki/Documentation/Nightly/Developers/ProjectForks

How to update the version of tclap ?

  1. Clone this repository and add a remote to the official project
git clone git://github.com/slicer/tclap
cd tclap
git remote add upstream https://git.code.sf.net/p/tclap/code
git fetch upstream
  1. Create a new branch following the convention slicer-YYYY-MM-DD-vY.Y.Z-SHA{N}

  2. Cherry-pick the Slicer specific commits from last branch. Resolve conflict as needed.

  3. To test the changes, locally rebuild SlicerExecutionModel.

  4. Publish the branch. (directly in this repo if you have push rights, or on a fork)

  5. Update SlicerExecutionModel and submit a pull request.

How to be granted push rights ?

Ask on https://discourse.slicer.org/

Questions

If you have questions, see https://discourse.slicer.org/