added cmake check for ARM and updated bash lines #206

Closed
jahway603 wants to merge 18 commits from jahway603:dev into dev
Collaborator

added cmake check for ARM and updated bash lines

added cmake check for ARM and updated bash lines
jahway603 added 18 commits 2 years ago
Poster
Collaborator

idk wtf happened with this pull request & first time using git stash, so who knows

idk wtf happened with this pull request & first time using git stash, so who knows
Owner

@jahway603 it's because you had an out of date dev branch and I did some of the stuff you did, so your changes created merge conflicts in many files. Git stash wasn't the culprit here

@jahway603 it's because you had an out of date dev branch and I did some of the stuff you did, so your changes created merge conflicts in many files. Git stash wasn't the culprit here
Owner

@jahway603 I suggest just working directly on the hush3.git dev branch and redo your change to check for cmake in build-arm.sh there. One way to "replay" your commit onto that branch is to do

git cherry-pick f356a3bd4b7825beea224d62d429f46b80e92c64

if you are working in a local git repo that has your commit in it. Or just copy+paste 😄

@jahway603 I suggest just working directly on the hush3.git dev branch and redo your change to check for cmake in build-arm.sh there. One way to "replay" your commit onto that branch is to do ``` git cherry-pick f356a3bd4b7825beea224d62d429f46b80e92c64 ``` if you are working in a local git repo that has your commit in it. Or just copy+paste :smile:
Owner

@jahway603 the reason this happened is because you made your single commit before doing "git pull", which changes the commit hashes of all subsequent commits. If you had done a "git pull" first then done your commit, this would have worked perfectly. Always "git pull" first, or like the git community says "always pull before you push" 😄

@jahway603 the reason this happened is because you made your single commit before doing "git pull", which changes the commit hashes of all subsequent commits. If you had done a "git pull" first then done your commit, this would have worked perfectly. Always "git pull" first, or like the git community says "always pull before you push" :smile:
Owner

This PR is fubar, it's much easier to start again than fix this. Closing out

This PR is fubar, it's much easier to start again than fix this. Closing out
duke closed this pull request 2 years ago
This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Loading…
There is no content yet.