General LTTng packages maintenance
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 7 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 7 patches the cover letter announces are in this archive.
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
Quoted 11 lines · Thomas Petazzoni
Dear Philippe Proulx,
Quoted 2 lines · Philippe Proulx
lttng-libust: rename package to lttng-ust
lttng-babeltrace: rename package to babeltraceTo 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.
For lttng-libust, I really think it's silly to rename it. Nobody will be
bothered by it.
Babeltrace on the other hand is more defendable. Are there any other packages
that we carry that produces traces that can be read by babeltrace?
Note also that there always has been pushback from Peter against gratuitous
renaming.
Quoted 5 lines
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.
Not only legacy handling, but also alphabetical ordering in package/Config.in.
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F