)]}' { "commit": "6d81ec706144d0126c2bc01b98b276a3451c57f4", "tree": "e50c6b9ea5fb5522f8f1ed47b397b64608a41905", "parents": [ "5904048b0caa1884ebffdd2bff9bdda71388df9a" ], "author": { "name": "Qijiang Fan", "email": "fqj@chromium.org", "time": "Tue Oct 27 07:53:05 2020" }, "committer": { "name": "Commit Bot", "email": "commit-bot@chromium.org", "time": "Tue Oct 27 16:53:19 2020" }, "message": "intel-wifi-fw-dump: use unversioned libchrome libraray.\n\nLibchrome is changing pkg-config and .so library name from\nxxxx-${libbase_ver}.{pc,so} to xxx.{pc,so}.\n\nLibchrome uprev rebuild will be handled by ebuild subslot change. And\nthere\u0027s no need to install multiple libchrome. Keeping libbase_ver\nsuffix will cause troubles on linking libraries when developers wants to\ntest locally emerge a-single-package without build_packages, after a\nlibchrome uprev. Especially in a case a package depends on another\npackage(library), and both depends on libchrome. Thus, removing\nlibbase_ver from suffix.\n\nBUG\u003dchromium:920513\nTEST\u003dCQ\n\nChange-Id: Icc3806ef7889f62be2f5add5622dc4d08c2c1df4\nReviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/intel-wifi-fw-dump/+/2500651\nReviewed-by: Hidehiko Abe \u003chidehiko@chromium.org\u003e\nCommit-Queue: Qijiang Fan \u003cfqj@google.com\u003e\nTested-by: Qijiang Fan \u003cfqj@google.com\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "09f7a2524268661b0e42d714d8ee40801b0b0e99", "old_mode": 33188, "old_path": "BUILD.gn", "new_id": "70d87c14573be3a4cabb7126d8b7dd6973e7f1f2", "new_mode": 33188, "new_path": "BUILD.gn" } ] }