| --- Log opened Sun Dec 17 00:00:02 2017 | ||
| bandvig | wallento: I see you update 'upstream' of openrisc/newlib periodically with fresh commits from NewLIB developer's repository. | 04:08 |
|---|---|---|
| bandvig | wallento: As I'm not very familiar with git, I would ask do you do this manually or some how automatically? | 04:08 |
| wallento | bandvig: Its a cron job on one of my servers | 04:08 |
| wallento | kind of this one: cd /gitmirror/newlib; git pull upstream master; git push mirror upstream | 04:09 |
| wallento | I use a certificate for this server, but I think actually its better to create a special account | 04:09 |
| wallento | and to be honest I did this to periodically merge that one into master then, but failed to do that then | 04:10 |
| bandvig | wallento: Could you clarify? Does it mean that upstream of NewLIB could not be merged to OR1K port without collision resolving or merging result couldn't be build? | 04:19 |
| wallento | it should be possible to merge it automatically | 04:20 |
| wallento | but in my experience whenever I thought that there is no problem, there always will be one.. | 04:21 |
| wallento | I will probably build a jenkins job that will try it and otherwise send a mail | 04:21 |
| wallento | its more a matter of the process | 04:21 |
| wallento | and discipline to fix stuff, as always | 04:22 |
| wallento | :) | 04:22 |
| bandvig | wallento: Well, understood. By the way. Could you organize similar job for 'upstream' of 'openrisc/binutils-gdb'? | 04:31 |
| bandvig | wallento: As OR1K binutils is upstreamed and periodically updated (thank Stafford and others :)), there shouldn't be a problem to build them. | 04:31 |
| bandvig | wallento: OR even use them as default branch. | 04:31 |
| wallento | oh, yeah, that was kind of there before I think. Actually the development model should probably be changed as you say | 05:19 |
| wallento | everything upstream should get feature branches off the current master in our repos | 05:25 |
| --- Log closed Mon Dec 18 00:00:04 2017 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!