Why only ASCII text files can be included in a RTC patch?
Hi All,
We need to create patch from RTC change so that we can apply it into other SCM systems, but there is one problem, binary file would not be included in the patch.
We also found that there is a --text option in a linux diff command to have the diff to treat all files as text, as a result, binary file would be included, so i am wondering why RTC don't have this option too?
Regards,
Makson
We need to create patch from RTC change so that we can apply it into other SCM systems, but there is one problem, binary file would not be included in the patch.
We also found that there is a --text option in a linux diff command to have the diff to treat all files as text, as a result, binary file would be included, so i am wondering why RTC don't have this option too?
Regards,
Makson
One answer
In almost all cases, normal "patch" logic does not work at all with
binary files. On the other hand, being able to apply "diff" to a binary
file is sometimes useful, to see what bytes are different.
Cheers,
Geoff
On 2/12/2012 8:23 PM, cdlee wrote:
binary files. On the other hand, being able to apply "diff" to a binary
file is sometimes useful, to see what bytes are different.
Cheers,
Geoff
On 2/12/2012 8:23 PM, cdlee wrote:
Hi All,
We need to create patch from RTC change so that we can apply it into
other SCM systems, but there is one problem, binary file would not be
included in the patch.
We also found that there is a --text option in a linux diff command to
have the diff to treat all files as text, as a result, binary file
would be included, so i am wondering why RTC don't have this option
too?
Regards,
Makson