-
Notifications
You must be signed in to change notification settings - Fork 18
Renamed files, directories, and targets to match beman standard #60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
[LIBRARY_NAMES] [CMAKE.PROJECT_NAME] [CMAKE.LIBRARY_NAME] [CMAKE.TARGET_NAMES] [DIRECTORY.INTERFACE_HEADERS]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Please check compiler explorer links included in root readme. After you merge this PR, an overnight deploy will be done automatically with compiler explorer, but we need to update our samples.
ps If you need to force deploy please ping an owner in compiler explorer - check link issue with #21
|
It's slightly annoying that many of the files are deleted and added instead
of being renamed, because they are short.
…On Tue, Sep 17, 2024, 06:10 Darius Neațu ***@***.***> wrote:
***@***.**** approved this pull request.
------------------------------
On CMakeLists.txt
<#60 (comment)>
:
LGTM 👍
Please check compiler explorer links included in root readme. After you
merge this PR, an overnight deploy will be done automatically with compiler
explorer, but we need to update our samples.
—
Reply to this email directly, view it on GitHub
<#60 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVNZ5Q2F4XN2H5NJ256J6TZW752TAVCNFSM6AAAAABOKRMOY6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGMBZGI4DKNJZG4>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
|
but I don't really feel strongly, just trying to see if I could make github cooperate better. |
|
I suppose to make #61 do what you want it to do, you'll have to not "squash and merge" the final result. |
|
Since "squash merge" is another way of spelling "merge conflict", yes. It
disconnects the history more generally and prevents merging on branches.
…On Tue, Sep 17, 2024, 11:48 David Sankel ***@***.***> wrote:
I suppose to make #61
<#61> do what you want it
to do, you'll have to not "squash and merge" the final result.
—
Reply to this email directly, view it on GitHub
<#60 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVNZ5UNURWXULOZWCQ7LHDZXBFLHAVCNFSM6AAAAABOKRMOY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJWGMYDSMRSGI>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
|
Is this PR still applicable? |
|
I think it's now obsolete. Landed a version that did the rename and edit in
two steps to preserve the rename in history.
…On Tue, Sep 24, 2024, 08:43 Darius Neațu ***@***.***> wrote:
Is this PR still applicable?
—
Reply to this email directly, view it on GitHub
<#60 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVNZ5XIN6AKEGRJQPRJ4O3ZYFM6VAVCNFSM6AAAAABOKRMOY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZRGE3DMMJZGM>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
|
Closing as obsolete. |
[LIBRARY_NAMES]
[CMAKE.PROJECT_NAME]
[CMAKE.LIBRARY_NAME]
[CMAKE.TARGET_NAMES]
[DIRECTORY.INTERFACE_HEADERS]