audit: don't recommend version aliases on --devel. #2483
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ilovezfs
approved these changes
Apr 11, 2017
|
@MikeMcQuaid: Shouldn't you report back to @neutric that Homebrew/homebrew-core#11462 has now been fixed by this PR in said issue's discussion feed? |
|
@RandomDSdevel I guess in the best of worlds, Mike would have crosslinked the way you did, but since he tagged me, I was made aware. If anything, I should have said thanks and sorry that I didn't take a stab at it myself. |
|
@neutric: Oh, of course. As for not working on a personal copy of what ended up being this PR yourself, I'm sure @MikeMcQuaid will understand; after all, it looks to me from your GitHub user profile that you've been quite busy elsewhere as of late! I'm glad to know you've been caught up on what's happened here, in any case. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As requested in #11462 by @neutric as this produces confusing, incorrect output.