| Summary: | Update to Qt 5.2.1 | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | syntheticpp |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | CC: | buildroot |
| Priority: | P5 | ||
| Version: | 2014.02 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: | Update to 5.2.1 | ||
|
Description
syntheticpp
2014-02-06 12:53:39 UTC
Created attachment 5222 [details]
Update to 5.2.1
Thanks a lot! However, could you submit patches to the mailing list? See the contribution process detailed at http://buildroot.org/downloads/manual/manual.html#_contributing_to_buildroot. Ah, yes. But the ml has way to much traffic for me. Ever thought about using gerrit? Yes, I believe we talked about Gerrit in the past, but the majority, if not all of the core developers as well as the maintainer, very much prefer a mailing list based review, rather than having to use a web-based tool to do reviews. Yes, a web interface is a draw-back. Maybe it is worth to create a buildroot-user ml. We discussed about creating a user-oriented mailing list at one of the latest Buildroot meeting. See http://elinux.org/Buildroot:DeveloperDaysELCE2013#Community_organization. The conclusion was: " We don't see a good way to split the lists at all, because a basic user is very quickly a basic developer and forcing them to see the patches is probably good." Moreover, we are talking about submitting patches here, so even if a buildroot user mailing list existed, you would have had to send your patches to the developer mailing list. |