jnemeth@ wrote: > On Nov 8, 6:01am, Izumi Tsutsui wrote: > } christos@ wrote: > } > } > | > If you want, I can give you access to the gcc-4.8.1 repo > } > | > so you can fix it yourself, just send me an ssh public key. > } > | > } > | Why isn't it in the public branch? > } > > } > We did not want to burden the tree with throway code. We'll import it once > } > it is done. > } > } IMO it's still better to have proper announcement in that case. > } (even developers don't know what's ongoing) > > We don't need announcments every time somebody starts working > on a project. Many developers work on all sorts of projects all > the time. Some pan out, some don't. When the developer has > something to show, we will know, either by an announcement if it > is something large, or by a commit if it is something small.
You don't need announcement, but less announcements, less feedback. If you don't need help for your project, you are right. I pointed out a problematic fix, then a person working on the project without announcement answered "you can fix it yourself." I don't know what's going on so less motivated. That's all. --- Izumi Tsutsui
