On Mon, Sep 16, 2013 at 03:35:04PM +0400, niXman wrote: > 2013/9/11 niXman: > > 2013/9/11 Tobias Ulmer: > >> Because it's work. Do you volunteer? > > > > Yes, I will, if someone will coordinate me. > > First of all, I need a description of what exactly problem is solved > > by each patch. >
Look, you are obviously a clueless newbie. Do you think we *like* having those patches there ? Don't you think we do routinely get them upstream when we can ? This takes time, mostly because it's very very difficult to work with this particular upstream, between insane rules (only commit to current), and very slow moving for low priority targets like OpenBSD. If you had half a clue, you would: - be able to read the commit messages for those patches and figure out what they do by yourself. - subscribe to the relevant gcc mailing-lists, and see what's currently hanging. - look at the source code for gcc-current upstream, and see for yourself what's committe/uncommitted and why. Here, you have enough pointers to keep you occupied for a while. Go grab clues, and come back where you have figured a few things out. Or just shut up. Currently, you're just an obnoxious pain.
