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

surprises in resolve #6143

Closed
graydon opened this issue Apr 30, 2013 · 5 comments
Closed

surprises in resolve #6143

graydon opened this issue Apr 30, 2013 · 5 comments
Assignees
@pcwalton
Labels
A-resolve Area: Path resolution metabug Issues about issues themselves ("bugs about bugs")

Comments

@graydon
Copy link
Contributor

graydon commented Apr 30, 2013

There are a number of ... surprises in resolve, which may be intentional, may not be, or may represent the need to make backwards-incompatible changes. I think they're related, but I'm not sure. I'm collecting them into a metabug here.

The ones I see are #4536 , #5238 , #5248 , #5269 and #3352 (though the last seems less likely related, it provokes a similarly-unclear "shouldn't this work?" feeling from me, and I'm not sure how to classify the bug)
@ghost ghost assigned pcwalton Apr 30, 2013
@m10e m10e mentioned this issue Jun 21, 2013
Closed
This was referenced Jul 2, 2013
Closed
Closed
Closed
Closed
Closed
Closed
@catamorphism
Copy link
Contributor

This appears to have been milestoned without being nominated. Re-nominating to move to milestone 1, well-defined.

@alexcrichton alexcrichton mentioned this issue Aug 12, 2013
Closed
@graydon
Copy link
Contributor Author

graydon commented Aug 22, 2013

accepted for well-defined milestone

@catamorphism catamorphism mentioned this issue Aug 29, 2013
Closed
@pnkfelix pnkfelix mentioned this issue Sep 4, 2013
Closed
@alexcrichton
Copy link
Member

Nominating to de-milestone. I believe the high-priority blocker is #8215, and there are otherwise associated issues, but I don't believe that they should be blockers.

@catamorphism
Copy link
Contributor

De-milestoning inf avor of more specific bugs

@huonw
Copy link
Member

huonw commented Jan 26, 2014

Triage: only #3352 and #6449 are left open; as such, I'm calling this done.

@huonw huonw closed this as completed Jan 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pcwalton pcwalton

Labels
A-resolve Area: Path resolution metabug Issues about issues themselves ("bugs about bugs")
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@graydon @alexcrichton @pcwalton @catamorphism @huonw