On 29/04/2015 8:05 pm, Hesham ALMatary wrote: > > This patch is needed, otherwise RSB wouldn't be able to build or1k > toolchain. I was thinking of getting rid of this hash as this patch > may be modified.
Normally a patch does not change and you increment a minor number or change a date in the file name. A user on a specific commit id of the RSB should be able to assume the files it references do not change. This is not always possible and I doubt it is that important in this case. > Or, we can refer directly to the latest or1k > gcc-4.9.2 [1] until they upstream it, as our patches are already > applied there. > > [1] https://github.com/openrisc/or1k-gcc/tree/or1k-4.9.2 > This is up to you and what makes your life easier. If you can select an archived version and get the RSB to download it that would be great. My preference is to be as far upstream as we can be where ever we can. I am sure you recognise the benefits this brings. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
