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

mhansen's 4.3.rc1 merge tree may have got ahead of wstein's #7764

Closed
williamstein opened this issue Dec 24, 2009 · 1 comment
Closed

mhansen's 4.3.rc1 merge tree may have got ahead of wstein's #7764

williamstein opened this issue Dec 24, 2009 · 1 comment
Assignees
@mwhansen
Labels
r: invalid t: bug

Comments

@williamstein
Copy link
Contributor

A block to take care of when the 4.3.1 merge cycle starts is that mhansen did some merging in I think

/scratch/mhansen/release/4.3/4.3.rc1

which might not have been reflected in the final 4.3 release. This could have resulted in tickets marked as closed when they weren't closed.

Component: misc

Issue created by migration from https://trac.sagemath.org/ticket/7764
@williamstein williamstein added this to the sage-4.3.1 milestone Dec 24, 2009
@jhpalmieri
Copy link
Member

comment:1

See #7769 for one possible such issue.

@mwhansen mwhansen removed this from the sage-4.3.1 milestone Jan 18, 2010
@jhpalmieri jhpalmieri mentioned this issue Jan 3, 2010
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mwhansen mwhansen

Labels
r: invalid t: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mwhansen @williamstein @jhpalmieri