General LTTng packages maintenance
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 of 7 patches 0 repliesNew
5 of 7 patches are in this archive. The cover letter announces 7.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | liburcu: bump to version 0.8.6 | +0 | 0 replies | |
| 2/7 | lttng-tools: bump to version 2.6.0 | +0 | 0 replies | |
| 3/7 | lttng-libust: bump to version 2.6.0 | +0 | 1 reply | |
| 4/7 | lttng-modules: bump to version 2.6.0 | +0 | 1 reply | |
| 5/7 | lttng-babeltrace: update Config.in's help | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [PATCH 0/7] General LTTng packages maintenance
Dear Philippe Proulx,
Quoted 2 lines · Philippe Proulx
lttng-libust: rename package to lttng-ust
lttng-babeltrace: rename package to babeltrace
To be honest, I am not sure about those ones. Renaming packages causes backward compatibility problems (that should be handled by adding the relevant entries in Config.in.legacy, which your patches is not doing), so renaming just for the sake of renaming, I'm not sure.
Since they lack the Config.in.legacy handling, I'll mark your patches as Changes Requested in our patch tracking system. When you'll resubmit them, I'll try to gather the opinion of other Buildroot developers to see what they think.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com