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

Merge with zf1s #96

Closed
glensc opened this issue Aug 3, 2020 · 12 comments
Closed

Merge with zf1s #96

glensc opened this issue Aug 3, 2020 · 12 comments

Comments

@glensc
Copy link
Collaborator

glensc commented Aug 3, 2020

Merge efforts with zf1s project:

it's code lives in monorepo:

but also code is split to sub-packages to benefit composer install of needed components only.

x-ref:

@Shardj
Copy link
Owner

Shardj commented Sep 18, 2020

I don't plan on doing a large merge at any point. If there are any important changes on zf1s that you feel are missing from this repo though please feel free to make a pull request

@Shardj Shardj closed this as completed Sep 18, 2020
@glensc
Copy link
Collaborator Author

glensc commented Sep 29, 2020

@glensc
Copy link
Collaborator Author

glensc commented Oct 2, 2020

Port needed to this repo:

@Shardj
Copy link
Owner

Shardj commented Oct 8, 2020

@glensc you know what you're doing so I've invited you as a contributor

@glensc
Copy link
Collaborator Author

glensc commented Oct 8, 2020

@Shardj thanks, but I'm only interested in improving zf1s side due to its package split and composer support and retaining support for legacy PHP versions and only providing continued support, not change/improve things.

However,
I'll keep providing two-way feedback on issues arising in zf1s project unless you tell me to stop.

Aside, would be nice to have opposite tracking too, or I'll just subscribe to this project updates.

@glensc
Copy link
Collaborator Author

glensc commented Dec 8, 2020

You can cherry-pick the commits from zf1s with something like this:

  1. go to PR page: https://github.com/zf1s/zf1/pull/39
  2. append .patch to the URL: https://github.com/zf1s/zf1/pull/39.patch
  3. download that locally: wget https://github.com/zf1s/zf1/pull/39.patch
  4. apply with git am: git am 39.patch
  5. git push, git, branch, etc

@glensc glensc mentioned this issue Dec 8, 2020
@Shardj
Copy link
Owner

Shardj commented Dec 8, 2020

@glensc thanks that's very helpful

@Shardj
Copy link
Owner

Shardj commented Dec 11, 2020

Doesn't seem to be working for me as the patch always fails, even after I fix the file paths. I'll just manually do this

@Shardj
Copy link
Owner

Shardj commented Dec 11, 2020

Ah it seems that for that particular patch we already fixed this code a while back

@glensc
Copy link
Collaborator Author

glensc commented Dec 13, 2020

ah, git am may not work if the project file layout is totally different. but you can use git commit --author 'XXX xxx@example.com' --date 'some timestamp' to preserve author and commit date.

@glensc
Copy link
Collaborator Author

glensc commented Oct 11, 2022

cherry-picking zf1s -> zf1-future is much easier when adding zf1s as remove, git is able to understand path renames.

example:

git remote add zf1s ../zf1s
git cherry-pick 232e616b8a3b4d278151f4d12214d3f5c43cc31b

later can manually compare both diffs:

git show 232e616b8a3b4d278151f4d12214d3f5c43cc31b > 1.patch
git show > 2.patch
diff 1.patch 2.patch

@glensc
Copy link
Collaborator Author

glensc commented Oct 11, 2022

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

No branches or pull requests

2 participants