Details
Diff Detail
- Build Status
Buildable 13329 Build 13329: arc lint + arc unit
Event Timeline
utils/docker/scripts/build_install_llvm.sh | ||
---|---|---|
84 | Do we want to sort the "cherries" in case they are not ordered? Does the order matter? |
utils/docker/scripts/build_install_llvm.sh | ||
---|---|---|
84 | Good point. Applying them in the sorted order is the most natural choice. |
utils/docker/scripts/build_install_llvm.sh | ||
---|---|---|
167 | I'd do the sorting in apply_cherrypicks. | |
208 | IIUC,$CHERRYPICKS is a list of cherries for all llvm sub-projects, and we try applying them on each project, even if some of them might not apply for certain projects. Is this safe with svn? Might worth a comment. |
utils/docker/scripts/build_install_llvm.sh | ||
---|---|---|
167 | Why not here? apply_cherrypicks is called multiple times, sorting outside of it seems natural. | |
208 | Fortunately we're good here, svn diff -c provides empty patches for revisions that don't touch specific repositories so we end up with a no-op. |
- Added a comment on applying cherrypicks to all repos
- Restructured the code to make it clear apply_cherrypicks works on a sorted list of cherrypicks
lg after code comment is added.
Do we want to mention this change in the doc?
utils/docker/scripts/build_install_llvm.sh | ||
---|---|---|
167 | Sorting inside apply_cherrypicks, you wouldn't need to worry about the state of CHERRYPICKS. The sorting here should also be really cheap. But up to you. This is shell script after all :) A comment in apply_cherrypicks requiring CHERRYPICKS to be sorted would still be nice. |
Do we want to sort the "cherries" in case they are not ordered? Does the order matter?