Skip to content
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

Update README_LINUX.md #4397

Merged
merged 1 commit into from
Jun 2, 2019
Merged

Update README_LINUX.md #4397

merged 1 commit into from
Jun 2, 2019

Conversation

novadeviator
Copy link
Contributor

Changed the url to Debian Multimedia team.

Purpose and Motivation

Types of changes

  • Documentation
  • Bug fix
  • New feature
  • Breaking change

To-do list

  • Code is tested
  • All tests are passing
  • Updated documentation
  • This PR is ready for review

Changed the url to Debian Multimedia team.
Copy link
Member

@dvzrv dvzrv left a comment

Choose a reason for hiding this comment

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

Thanks!

@mossheim
Copy link
Contributor

mossheim commented Jun 2, 2019

Thanks! Please rebase this against 3.10 -- see our contributor's guide for more information.

@nhthn nhthn added the comp: help schelp documentation label Jun 2, 2019
@nhthn nhthn added this to the 3.10.3 milestone Jun 2, 2019
@novadeviator
Copy link
Contributor Author

Can I rebase this commit (i have already deleted my patch/branch from my profile) or must I pull the 3.10 branch and make the edit again? If I can rebase the commit itself, I'm not sure I know how. In other case, should I pull devel branch, make an edit, commit, rebase into 3.10 and then force push? Apologies for my cluelessness.

@patrickdupuis patrickdupuis merged commit f54358b into supercollider:develop Jun 2, 2019
@novadeviator
Copy link
Contributor Author

novadeviator commented Jun 2, 2019

ok i was spending couple of hours trying to follow instruction on contributor's guide,making fork, cloneing to my local machine, creating branch and then failing at rebasing to 3.10. and now I see this was resolved by someone? what just happened? confused, but I don't want to take too much time from devs.

edit: the question is how should i do this next time?

@nhthn
Copy link
Contributor

nhthn commented Jun 2, 2019

sorry about the confusion! SC development is based on the git-flow model, where development takes place mainly on two branches: we merge changes into the 3.10 branch if it's a bug fix or something nonintrusive to be released in the next 3.10.x version, and we merge new features and breaking changes into develop to be released in 3.11.

if you make a new PR against develop when it's really a bug fix that should go against 3.10, we have two different strategies:

  1. have the author rebase it against 3.10
  2. let it be merged into develop, and then someone will cherry-pick it onto the 3.10 branch

there's been a little disagreement on whether we should go with 1 (which puts responsibility on the PR author to do a tricky git operation) or with 2 (which puts responsibility on maintainers, and we're currently grinding through a backlog of 50+ PRs). brian prefers requesting the PR author, while i'm pro-cherrypick, and i suggested to patrick to do the merge. sorry you got caught in the crossfire here.

also if you need any help with git stuff, feel free to ask on slack!

nhthn pushed a commit that referenced this pull request Jun 3, 2019
@novadeviator
Copy link
Contributor Author

novadeviator commented Jun 3, 2019 via email

@nhthn
Copy link
Contributor

nhthn commented Jun 4, 2019

yes, that'd be because you don't have the 3.10 branch. git fetch origin 3.10 should do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp: help schelp documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants