-
Notifications
You must be signed in to change notification settings - Fork 55
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
Add Appveyor and Travis CI (if needed) #46
Comments
@Lastique Please set milestone to v1.66.0 for this issue. |
@Lastique I just noticed that my company email was used as the commit author instead of my apache.org email. It should be "jking@apache.org". Is there any way to fix that in the history, or is it impossible now that it was merged? |
It is possible to rewrite history on develop, but that will cause inconsistencies with the superproject (i.e. some commits in the superproject will be referring to a non-existent commit in Boost.WinAPI). Unless you really want to change that email (e.g. it might get you in trouble with your employer or something) I would prefer to avoid doing this. Please, let me know if you still want me to do this. |
I figured it would be painful - we'll let it be.
…On Tue, Sep 19, 2017 at 4:37 PM, Andrey Semashev ***@***.***> wrote:
It is possible to rewrite history on develop, but that will cause
inconsistencies with the superproject (i.e. some commits in the
superproject will be referring to a non-existent commit in Boost.WinAPI).
Unless you really want to change that email (e.g. it might get you in
trouble with your employer or something) I would prefer to avoid doing
this. Please, let me know if you still want me to do this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#46 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALOdbZ8aXFQ-qXy14vlB6xD3vor7Evhuks5skCYhgaJpZM4PW6D9>
.
|
We need a suite of tests that exercise the large number of compile-time branches in the project and ensure compatibility with Visual Studio versions (2010 through 2017) and older MinGW 32-bit and newer MinGW-x64.
The text was updated successfully, but these errors were encountered: