rtcTo/rtc2git
A tool made for migrating code from an existing IBM's RTC SCM repository into a Git repository
4 Releases
Latest: 9y ago
Version 2.0v2.0Latest
WtfJoke·9y ago·October 4, 2016📋 Changes
- Check ignored files which still are present [#72](https://github.com/rtcTo/rtc2git/issues/72)
- Specify user/password on the command line [#69](https://github.com/rtcTo/rtc2git/issues/69)
- .jazzignore -> .gitignore [#66](https://github.com/rtcTo/rtc2git/issues/66)
- Configuration of conflict resolver [#55](https://github.com/rtcTo/rtc2git/issues/55)
- Ability to use -i when loading a workspace [#50](https://github.com/rtcTo/rtc2git/issues/50)
- Link commits with Issue-System (Jira/Github/BitBucket) [#48](https://github.com/rtcTo/rtc2git/issues/48)
- Provide configuration with fallback-values [#47](https://github.com/rtcTo/rtc2git/issues/47)
- Decide if migration should be resumed or is started [#42](https://github.com/rtcTo/rtc2git/issues/42)
- + 74 more
Version 1.1v1.1
WtfJoke·11y ago·June 14, 2015📋 Changes
- Automatic determiniation/creation of oldest workspace
- Supports custom encoding
- Logic to avoid merge-conflicts by accepting multiple changesets
- User can decide wheter he wants to use lscm/scm/fec as RTC Command Line Interface
Version 1.0v1.0
WtfJoke·11y ago·May 26, 2015Stable Release. Can be used for migrating big/small repositories.
v0.9WithoutReliableHistoryPre-release
WtfJoke·11y ago·May 26, 2015Stable release, however the feature of providing a reliable history from the user isnt there (see https://github.com/WtfJoke/rtc2git/wiki/Getting-your-History-Files#why-do-i-need-to-provide-the-history-files for details. For small projects usable.