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

promote [iterator.range] to rSec1 not rSec2 #4

Closed
wants to merge 22 commits into from

Conversation

jwakely
Copy link
Member

@jwakely jwakely commented Jan 17, 2012

this renumbers [iterator.range] from 24.6.5 to 24.7, as it shouldn't be a sub-clause of [stream.iterators]

@sdutoit
Copy link
Contributor

sdutoit commented Jan 17, 2012

Seems once again a bunch of other commits got pulled in; do you think you can submit another pull request with just the given commit?

@jwakely
Copy link
Member Author

jwakely commented Jan 17, 2012

yeah I noticed that, but the diff shows only a one-line change. I'm not sure why the other commits appear as unmerged.
I'll see if I can tell what I've done wrong and try again

@sdutoit
Copy link
Contributor

sdutoit commented Jan 17, 2012

I'm guessing the issue is that I didn't pull in those commits directly but merged them into a single commit using a rebase (this mostly keeps my bookkeeping simpler). You could probably rebase your repo, or I expect in creating the pull request there must be some way to only request the single commit.

@jwakely
Copy link
Member Author

jwakely commented Jan 19, 2012

ok, I've rebased and will send another pull request

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

2 participants