Hi,
Samphan Raruenrom wrote:
Hi,
I usually find someone says in an issue, e.g. issue 41671 - "fixed in cws i18n16".
I understand that the patch will be in the branch cws_src680_i18n16 with
the task id #i41671# in the commit message. But how can I find which
file(s) the patch change. How can I extract the patch so I can apply
to my source tree?
You can't do that easily. The EIS information Mathias mentioned is there only when the CWS is already merged to the main trunk. And this information, derived from the commit messages does not always tell the entire truth. Moreover the child workspace system is designed to encourage putting multiple fixes in one area in the code together into one child workspace. That means that changes for one bug often don't apply cleanly to the trunk version of the file, as they were applied to a file that already had other fixes.
Summarizing this, it is usually better to merge an entire child workspace rather than isolated bug fixes. Child workspaces can be merged easily usign cvs: As you reckognized the CWS version is on branch cws_<mws>_<cwsname> (e.g. cws_src680_i18n16). The trunk version from which this is branched is tagged as CWS_<MWS>_<CWSNAME>_ANCHOR (e.g. CWS_SRC680_I18N16_ANCHOR). Thus you can easily use cvs update to join the changes from the CWS (cvs update -j<ANCHOR-TAG> -j<BRANCH-TAG>). Attention: Use the anchor tag instead of joining the entire branch, because a so-called 'resync' may be used to merge changes from the trunk to the cws branch.
BTW: A cws typically only contains only selected modules. Only files in those modules are tagged. You can use EIS to find out the list of modules for a given cws.
HTH, Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
