Skip to content
This repository was archived by the owner on Mar 27, 2019. It is now read-only.

Patch 9767 applied#60

Open
ticaje wants to merge 1 commit into
firegento:magento-1.9.3.2from
ticaje:magento-1.9.3.2
Open

Patch 9767 applied#60
ticaje wants to merge 1 commit into
firegento:magento-1.9.3.2from
ticaje:magento-1.9.3.2

Conversation

@ticaje

@ticaje ticaje commented Jun 5, 2017

Copy link
Copy Markdown

I use this repository on a daily basis so i'd like to contribute with the new patch applied

@razbakov

razbakov commented Jun 7, 2017

Copy link
Copy Markdown

@ticaje thank you for contribution! It appears that this patch addresses the same problem as v.1.9.3.3. Can you please check if https://github.com/firegento/magento/releases/tag/v1.9.3.3 is the same? Or would you like to have an additional patch version in 1.9.3.2?

@ticaje

ticaje commented Jun 22, 2017

Copy link
Copy Markdown
Author

Yes, it seems to be included in the branch 1.9.3.3, even though it would be nice to merge my ammendments into 1.9.3.2's since there are many people using this branch yet. The idea is to update composer file in order to update the branch but i guess those people are not using yet composer, it's astonishing but true.

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.

2 participants