Skip to content
This repository has been archived by the owner on Dec 18, 2022. It is now read-only.

RFC: Fetch and merge upstream changes #152

Closed
wants to merge 5 commits into from
Closed

RFC: Fetch and merge upstream changes #152

wants to merge 5 commits into from

Conversation

falkTX
Copy link
Contributor

@falkTX falkTX commented Jul 8, 2021

Brings changes from upstream master branch.
README.md and 3RDPARTY.txt files had conflicts.
README.md conflicts were easily resolved.
3RDPARTY.txt file is not present upstream, do we need it? Or delete it as well? (which I did here, not sure if correct)

  • The code in this pull request is licensed under "GPLv2 or any later version"
  • I made sure the code compiles on my machine
  • I made sure there are no unnecessary changes in the code
  • I made sure the title of the PR reflects the core meaning of the issue you are solving
  • I made sure the commit message(s) contain a description and answer the question "Why do those changes fix that particular issue?" or "Why are those changes really necessary as improvements?"

SteveDaulton and others added 4 commits July 4, 2021 20:02
When importing an AUP project, selLow and selHigh may not be defined
in the project. If not defined, this causes an error on initialising
Nyquist. See: https://forum.audacityteam.org/viewtopic.php?f=48&t=118940
... in particular so that warnings on exit in the debug build on Windows are
suppressed.

Maybe it's not important to suppress them.  Or maybe they suggest all is not
correct in the MSVC implementation of this C++17 feature?
- James, Roger, Steve and Greg move to emeritus
- Trademark text updated.
- Dev team description changed.
This bug still available in case: using old settings file or manual set it into settings file.
@falkTX
Copy link
Contributor Author

falkTX commented Jul 8, 2021

Note: in order to keep proper history if these PRs are merged, they need to be in "rebase and merge" mode.

@Semisol
Copy link
Contributor

Semisol commented Jul 8, 2021

Note: in order to keep proper history if these PRs are merged, they need to be in "rebase and merge" mode.

image

@falkTX
Copy link
Contributor Author

falkTX commented Jul 8, 2021

That is very odd. I just cloned a brand new tenacity repo and created this PR, it should be 100% clean..

@fossdd
Copy link
Member

fossdd commented Jul 8, 2021

In general I would suggest the team always to rebase. patches on sr.ht mailing lists should should also applied with git am which also rebases it.

For additional info see https://git-rebase.io/ by Drew DeVault.

@falkTX
Copy link
Contributor Author

falkTX commented Jul 8, 2021

I can manually merge things from CLI without issues, assuming not using --no-ff as there is already a merge commit (needed for the README conflicts)

@falkTX
Copy link
Contributor Author

falkTX commented Jul 8, 2021

Let me try again, I think I might have done something wrong...

@falkTX
Copy link
Contributor Author

falkTX commented Jul 8, 2021

Recreated the repo now and force pushed, maybe good now?

Copy link

@adrianheine adrianheine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks mostly good

CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you delete this file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because it generates merge conflicts even though the file is not present upstream.
Do we need it?

@@ -54,5 +52,3 @@ void NonInterferingBase::operator delete(void *ptr, std::align_val_t al)
// Call through to default operator
::operator delete(p);
}

#endif

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't say anything about this

{ return operator new(count, al); }
static void operator delete(
void *ptr, std::align_val_t al, int, const char *, int)
{ return operator delete(ptr, al); }

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't say anything about this either

@falkTX
Copy link
Contributor Author

falkTX commented Jul 8, 2021

Note that besides a little change in the README (linking to the site, similar to what audacity does) none of the changes here are from me but upstream

@emabrey
Copy link
Member

emabrey commented Jul 10, 2021

What license are the upstream changes we are pulling?

@Semisol
Copy link
Contributor

Semisol commented Jul 11, 2021

Small reminder: Please sign off your commits. Do this by:

git rebase --signoff HEAD~<amount of commits not signed off>
git push --force-with-lease

@falkTX falkTX closed this Jul 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants