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

[range.join.with.iterator] Add missing 'template' keyword prior to dependent template name 'emplace' #5455

Merged
merged 1 commit into from Apr 20, 2024

Conversation

hewillk
Copy link
Contributor

@hewillk hewillk commented May 6, 2022

No description provided.

@jensmaurer
Copy link
Member

@jwakely, this looks reasonable (although it clutters the presentation).

@wg21bot wg21bot added the needs rebase The pull request needs a git rebase to resolve merge conflicts. label Aug 19, 2022
@hewillk
Copy link
Contributor Author

hewillk commented Apr 19, 2024

Note that the emplace() in concat_view's specification has the template keyword, so this PR should help with consistency.

@jensmaurer
Copy link
Member

We still need a rebase + force-push.

@jensmaurer
Copy link
Member

jensmaurer commented Apr 19, 2024

Something odd happened with the rebase; we now have 6k lines changes in containers.tex which shouldn't be in this patch. And we have 10 commits.

Again, please squash all the changes you want to have in this pull request (and nothing else) to a single commit and force-push. "git rebase -i main" might help.

@hewillk
Copy link
Contributor Author

hewillk commented Apr 19, 2024

Sorry, I think I messed up.

@hewillk
Copy link
Contributor Author

hewillk commented Apr 19, 2024

Because I always submit PRs on the git web page, I haven't actually used git locally for a long long time, so I need to recall these steps. (I've never squash or rebase PRs because I'm not familiar with it, sorry about that. I mostly use perforce system.)

@jensmaurer
Copy link
Member

"This branch has conflicts that must be resolved"

@hewillk
Copy link
Contributor Author

hewillk commented Apr 20, 2024

"This branch has conflicts that must be resolved"

Thanks for the pointers.
Now I think these conflicts should be resolved. The current question is how do I merge those disorganized 13 commits into 1 commit online?

@jensmaurer jensmaurer removed the needs rebase The pull request needs a git rebase to resolve merge conflicts. label Apr 20, 2024
@jensmaurer
Copy link
Member

@jwakely, could you please have a look?

Also, this MUST be squashed when merging. The commit history is ... frightening.

@jwakely
Copy link
Member

jwakely commented Apr 20, 2024

I'm not sure why github thinks it needs rebasing, it squashes cleanly for me.

Something like this:

git checkout -b pr/5455 origin/main
git fetch  https://github.com/hewillk/draft main-2
git merge --squash FETCH_HEAD
git commit
git push --force git@github.com:hewillk/draft.git  HEAD:main-2

@jwakely
Copy link
Member

jwakely commented Apr 20, 2024

Hmm, except that has spurious unrelated changes. What did you do?!

Copy link
Member

@jwakely jwakely left a comment

Choose a reason for hiding this comment

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

Rebased and force pushed to keep just the commit we want.

@hewillk
Copy link
Contributor Author

hewillk commented Apr 20, 2024

Hmm, except that has spurious unrelated changes. What did you do?!

I don't know, I just did something terrible that I can't remember. I may have rebase the wrong branches or something, or reset something wrong or something. Anyway, I'm sorry for the unspeakable clutter.

And, again, thanks for the instant redemption.

@jwakely
Copy link
Member

jwakely commented Apr 20, 2024

What I did was:

git checkout -b pr/5455 origin/main
git fetch  https://github.com/hewillk/draft main-2
git merge --squash FETCH_HEAD
git checkout HEAD -- lib-intro.tex threads.tex time.tex # drop the unwanted changes
git commit # and remove all the unrelated cruft in the commit message
git push --force git@github.com:hewillk/draft.git  HEAD:main-2

@jwakely
Copy link
Member

jwakely commented Apr 20, 2024

It probably would have been easier to just do:

git checkout main
git cherry-pick 573319cc006a3082128d240494efdf8eb2f46cd0

i.e. just cherry-pick the one good commit from that messy series of 13 commits. Then force-push that to main-2

@jensmaurer jensmaurer merged commit 5d4d950 into cplusplus:main Apr 20, 2024
2 checks passed
@hewillk hewillk deleted the main-2 branch April 21, 2024 06:48
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

4 participants