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
3.6.4: Correcting encoding mismatch for helpsites.xml #12507
Conversation
* handeling for mcrypt and openssl * Language changes suggested bei Brian
I have tested this item ✅ successfully on 037bd4a This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12507. |
This comment was marked as abuse.
This comment was marked as abuse.
RTC based on testing. Thanks! This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12507. |
Implemented with: 6f86ebb as this PR is broken anyhow. |
This comment was marked as abuse.
This comment was marked as abuse.
It's because he changed the base branch and because JMs PR was based on the 3.6.4 branch it drug all the other commits from there over too. |
Yes i have changed the base so i can merge it into staging and not the 3.6.4 branch. Is there any better way instend of changing the base (that broken this PR)? |
Manually commit it (with proper author attributes). It's like opening a PR designed for something in the 3.7.x branch against staging when your branch was branched from 3.7.x, the PR is going to show all the commits not in the target branch. So similar thing here; the PR was against the 3.6.4 branch which has commits not in staging then you changed the base branch so it included those commits not in staging because JM branched from the 3.6.4 branch. |
Ok thanks. And thanks for the help / explanation. |
The other way to think of it. You're proposing to merge a remote branch into a base branch. That remote branch has certain commits not in the base branch, and that is what you want to merge. So when you change the base branch you want to merge that remote branch into, you're changing the commits you're proposing be merged potentially. It's kinda how git works at the underlying layer. You aren't explicitly sending a pull request for X commits. GitHub's UI just does a great job showing that stuff. |
that was supposed to be mer ged in 3.6.4... |
George told me this should not go into 3.6.4 |
He was mistaking. It had to go into 3.6.4. It is related to joomla/update.joomla.org#27 @rdeutz can make new packs with this change. It is not a big deal. I had already told him. |
This comment was marked as abuse.
This comment was marked as abuse.
We decided not to merge it, all good. |
mantainers please remove 3.7.0 label here |
Changed the encoding of the file as
Français
was badly displayed.@rdeutz
You can merge. I am creating the same in joomlaupdate now.