Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

How to keep file's update history and annotations when copy RTC project files

Questions
Tags
Users
Badges
kelly hu
(21●2●16) Feb 24 '16, 10:35 p.m.
Hi RTC admins,
From RTC SCM, I can find RTC project files' history and annotation which make me easily find who/when/what reasons that we change the code. Currently I want to copy some project files to start a new version development, my question is - can we keep all previous files' history and annotation in the new version project files? Does RTC support this function?
Thanks for your guidance and feedback.
Kelly

0 votes

Comments
Arun K Sriramaiah
Feb 25 '16, 3:08 a.m.
Hi Kelly, Please find the link below and let me know does it helps. https://jazz.net/forum/questions/117643/how-to-exportimport-source-code-history-from-one-rtc-instance-to-another Regards, Arun.

kelly hu
Feb 25 '16, 4:03 a.m.
Hi Arun, Thanks for the feedback, we have tried duplicate stream function and found it difficult to maintain so many streams with multiple components, and our aim is to copy some component under the same stream, does RTC support copy component function ? thanks.

Arun K Sriramaiah
Feb 25 '16, 4:45 a.m.
Could you please let us know from where to where you are copying the components with in the RTC. If RTC is source == Which is the target server ? and how are trying to copy now.

kelly hu
Feb 25 '16, 4:56 a.m.
We just want to copy one component under  the same stream and repository, then use the new component as a new version, no need to copy component from another server/repository, do you have any suggestions? thanks a lot.

2 answers
5,731 views
0 votes

2 answers

Permanent link
Arun K Sriramaiah
(3.2k●2●37●77) Feb 25 '16, 5:28 a.m.
Hi Kelly,

Please try with move in repository option and find the link below and let us know does it helps.

http://www-01.ibm.com/support/docview.wss?uid=swg21673644

Regards,
Arun.

0 votes

Permanent link
Geoffrey Clemm
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER (30.1k●3●34●35) Feb 26 '16, 5:38 p.m.
There are very, very few circumstances where it is a good idea to "copy" a component.
Please describe in detail the problem you are trying to address, and we can provide a recommendation (and it is very unlikely that recommendation will involve copying the component :-).

There are cases where there are a set of files that you want to move to another component, and for those cases you would use the "move in repository" function mentioned by Arun, but you would not use that function to "copy" a component.

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,147

Question asked: Feb 24 '16, 10:35 p.m.

Question was seen: 5,731 times

Last updated: Feb 26 '16, 5:38 p.m.

Confirmation Cancel Confirm