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.

Sign up for GitHub

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

Jump to bottom

keeping pg up to date #92

Closed
mgage opened this issue Jan 26, 2014 · 1 comment
Closed

keeping pg up to date #92

mgage opened this issue Jan 26, 2014 · 1 comment

Comments

@mgage
Copy link
Member

mgage commented Jan 26, 2014

pg is looking fairly good. release/2.8.1 is not missing anything from the master branch.
The commits missing from develop will be restored when we merge release/2.8.1 back in to develop. (I think. :-) )
@dpvc
Copy link
Member

dpvc commented Jan 26, 2014

Yes, there have been enough pulls from master into branches that were merged into release/2.8.1 to mean release/2.8.1 is not behind master. You are correct that merging release/2.8.1 into develop will bring those changes into develop at that point.

@goehle goehle closed this as completed May 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dpvc @mgage @goehle