Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upfixing fpsWhen in a post-0.15 future #209
Conversation
jvoigtlaender
added some commits
Mar 12, 2015
evancz
closed this
Apr 29, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jvoigtlaender
Apr 30, 2015
Contributor
Does this mean we are not going to have a future with a separate stream concept?
|
Does this mean we are not going to have a future with a separate stream concept? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evancz
Apr 30, 2015
Member
Oops, I cleaned out a bunch of branches that were zero commits in front of master not realizing that future was purposely behind. Do you happen to know which commit corresponds to the future branch so we can tag it?
|
Oops, I cleaned out a bunch of branches that were zero commits in front of master not realizing that |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jvoigtlaender
Apr 30, 2015
Contributor
Oh. I'm not even sure I know how git is working, so "a commit corresponding to a branch"? Well, my best guessing would go like that: My branch in which I was working for this PR here, and which was diffed against the future branch to make this PR, currently ends with this commit. So maybe that is the one you are looking for. It seems that would make sense, because it happened one day before the current master branch has a commit titled "Get rid of Stream module, revert to 0.14 style Signals".
|
Oh. I'm not even sure I know how git is working, so "a commit corresponding to a branch"? Well, my best guessing would go like that: My branch in which I was working for this PR here, and which was diffed against the |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jvoigtlaender
Apr 30, 2015
Contributor
Yes, this must be the commit you want. It has the exact same diff against my "fixing branch" as is shown in this PR here.
|
Yes, this must be the commit you want. It has the exact same diff against my "fixing branch" as is shown in this PR here. |
jvoigtlaender commentedApr 9, 2015
This is retargeting PR https://github.com/elm-lang/core/pull/198/ towards the
futurebranch.