OK so just one final question to be clear: This patch was created from trunk with config,sub and config.guess copied from GNU config upstream. If you say, that I should just modify bits for my port, then this patch is still bad (since it modifies much more).
Then when those scripts get copied 'as they are' from GNU config? Only for newly created branches? 2016-05-13 22:18 GMT+02:00 Mike Stump <mikest...@comcast.net>: > On May 13, 2016, at 11:50 AM, Jakub Sejdak <jakub.sej...@phoesys.com> wrote: >> >> OK I understand. So am I right, that in such a case there is no way to >> introduce new OS targets to branch 4.9 and 5? > > No. You just hand edit in the bits you need for your port, and seek approval > for that. > > In general, all new work goes into trunk, first. Once it is there, then you > can back port to the first oldest release branch. Once there, then you can > back port to the next oldest and so on. If it can't make it into a branch, > it can't go onto the next oldest branch. > > So, be be concrete, get 5 in first, then ask for 4.9. Get 6 in first, then > ask for 5. Get trunk in first, then ask for 6. > >> What about 6 branch and trunk? > > 6 would have the same answer as 4.9 and 5. For trunk, import from upstream > is the usual way to pick up that work. > >> On the other hand: this is my first patch and I'm not quite familiar >> with the procedure of applying patches to upstream. Who should upload >> my patch, when it gets accepted? > > Anyone with write access.
