mks

MKS/ PTC Integrity Source equivalent to svn:ignore

a 夏天 提交于 2019-12-06 04:28:20
问题 We use MKS/PTC Integrity for source control at my work. Is there an equivalent to the svn:ignore flag from subversion? Essentially, I'd like a way to tell MKS to ignore a folder / file for changes. (Ie., our compiler output folders, etc). 回答1: You can set global ignore filters by opening the following menu: File->Edit Preferences... and then selecting: Configuration Management->Views->Non-Members View An alternative is to select: Sandbox->Views->View Non-Members and then right-click a file

MKS/ PTC Integrity Source equivalent to svn:ignore

人盡茶涼 提交于 2019-12-04 10:24:01
We use MKS/PTC Integrity for source control at my work. Is there an equivalent to the svn:ignore flag from subversion? Essentially, I'd like a way to tell MKS to ignore a folder / file for changes. (Ie., our compiler output folders, etc). You can set global ignore filters by opening the following menu: File->Edit Preferences... and then selecting: Configuration Management->Views->Non-Members View An alternative is to select: Sandbox->Views->View Non-Members and then right-click a file and Exclude by [Name|Extension] This is only filtering the Non-members View. See http://communities.ptc.com

Is it possible to import an MKS Integrity repository into git?

删除回忆录丶 提交于 2019-12-04 08:30:56
问题 I need only the source tree and its history. I don't care for the requirements/issues stuff for now. I played a bit witth the command line to figure out if I could get a list of change packages for the trunk and some of the dev paths. I thought it should be possible to extract a diff for every change package and use that to replay all the changes since the first commit in git. Something like this: get first commit and add it to git get next CP get diff for CP apply diff to git working dir add

Is it possible to import an MKS Integrity repository into git?

*爱你&永不变心* 提交于 2019-12-02 23:47:55
I need only the source tree and its history. I don't care for the requirements/issues stuff for now. I played a bit witth the command line to figure out if I could get a list of change packages for the trunk and some of the dev paths. I thought it should be possible to extract a diff for every change package and use that to replay all the changes since the first commit in git. Something like this: get first commit and add it to git get next CP get diff for CP apply diff to git working dir add and commit changes to git repeat with (2.) until last CP You could also repleace change package with