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

3.6.4: Correcting encoding mismatch for helpsites.xml #12507

Closed
wants to merge 4 commits into from

Conversation

infograf768
Copy link
Member

@infograf768 infograf768 commented Oct 22, 2016

Changed the encoding of the file as Français was badly displayed.

@rdeutz

You can merge. I am creating the same in joomlaupdate now.

Thomas Hunziker and others added 3 commits October 20, 2016 22:02
@andrepereiradasilva
Copy link
Contributor

I have tested this item ✅ successfully on 037bd4a

on review


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12507.

@PhilETaylor

This comment was marked as abuse.

@zero-24
Copy link
Contributor

zero-24 commented Oct 22, 2016

RTC based on testing. Thanks!


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/12507.

@joomla-cms-bot joomla-cms-bot added the RTC This Pull Request is Ready To Commit label Oct 22, 2016
@zero-24 zero-24 changed the base branch from 3.6.4 to staging October 22, 2016 20:26
@zero-24
Copy link
Contributor

zero-24 commented Oct 22, 2016

Implemented with: 6f86ebb as this PR is broken anyhow.

@zero-24 zero-24 closed this Oct 22, 2016
zero-24 added a commit that referenced this pull request Oct 22, 2016
@zero-24 zero-24 removed the RTC This Pull Request is Ready To Commit label Oct 22, 2016
@PhilETaylor

This comment was marked as abuse.

@mbabker
Copy link
Contributor

mbabker commented Oct 22, 2016

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.

@zero-24
Copy link
Contributor

zero-24 commented Oct 22, 2016

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)?

@mbabker
Copy link
Contributor

mbabker commented Oct 22, 2016

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.

@zero-24
Copy link
Contributor

zero-24 commented Oct 22, 2016

Manually commit it (with proper author attributes).

Ok thanks. And thanks for the help / explanation.

@mbabker
Copy link
Contributor

mbabker commented Oct 22, 2016

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.

@infograf768
Copy link
Member Author

that was supposed to be mer ged in 3.6.4...

@zero-24
Copy link
Contributor

zero-24 commented Oct 23, 2016

George told me this should not go into 3.6.4

@infograf768
Copy link
Member Author

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.

@PhilETaylor

This comment was marked as abuse.

@rdeutz
Copy link
Contributor

rdeutz commented Oct 23, 2016

We decided not to merge it, all good.

@andrepereiradasilva
Copy link
Contributor

mantainers please remove 3.7.0 label here

@brianteeman brianteeman removed this from the Joomla 3.7.0 milestone Nov 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants