Skip to content

Conversation

@datibbaw
Copy link
Contributor

This complements an earlier discussion on the mailing list to finally remove ereg altogether.

@laruence
Copy link
Member

Nice~

@Majkl578
Copy link
Contributor

💯
But the commits should be in reverse order imho - first, remove dependencies and port code which uses ereg, then remove ereg itself afterwards.

@datibbaw
Copy link
Contributor Author

@Majkl578 This is easier; remove it first and see what breaks :)

@Majkl578
Copy link
Contributor

Yup, but it's not a correct workflow. Also, git rebase magic is pretty easy solution for reordering commits. ;)

@datibbaw
Copy link
Contributor Author

@Majkl578 I guess we're just going to have to agree to disagree then.

Copy link
Member

Choose a reason for hiding this comment

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

Superfluous check, PCRE is always enabled.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Coming to think of it, the check for mbstring extension is kind of unnecessary as well :)

@datibbaw datibbaw force-pushed the kill-ereg branch 2 times, most recently from 4684406 to 610ef5d Compare September 11, 2014 02:47
@datibbaw
Copy link
Contributor Author

Merged into master with 86de796

@datibbaw datibbaw closed this Sep 11, 2014
@datibbaw datibbaw deleted the kill-ereg branch September 11, 2014 02:48
@staabm
Copy link
Contributor

staabm commented Sep 11, 2014

Reverted with 1981dd9

@datibbaw datibbaw mentioned this pull request Sep 11, 2014
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.

6 participants