Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Re-enable MIT.xml (continue from #12002) - #14169

Merged
J0WI merged 2 commits into
masterfrom
re-mit
Jan 4, 2018
Merged

Re-enable MIT.xml (continue from #12002)#14169
J0WI merged 2 commits into
masterfrom
re-mit

Conversation

@J0WI

@J0WI J0WI commented Jan 3, 2018

Copy link
Copy Markdown
Contributor

No description provided.

J0WI added 2 commits January 3, 2018 15:30
* Re-run Travis

* Update MIT.xml

* Update MIT.xml

* Update MIT.xml

* Update MIT.xml

* Update MIT.xml

* Update MIT-mismatches.xml

* Update MIT.xml

* Update MIT.xml

* Update MIT-mismatches.xml

* Update MIT.xml

* Update MIT.xml

* Update MIT.xml

* Update MIT.xml

* Update MIT.xml
@Hainish Hainish added the top-1k label Jan 3, 2018
@J0WI
J0WI merged commit 3c75f10 into master Jan 4, 2018
@J0WI
J0WI deleted the re-mit branch January 4, 2018 01:12
@jeremyn

jeremyn commented Jan 4, 2018

Copy link
Copy Markdown
Contributor

@J0WI For what it's worth, I don't agree with how you handled this. As I wrote in #12002 (comment), I think you should have resubmitted the old PR with your extra changes as a new PR and then waited for someone else to review it. Instead you effectively self-committed many changes to a complicated top-1k ruleset.

I'm not accusing you of anything or whatever, but I think we should discuss this as a group first if you plan on taking this approach to future abandoned / @ghost PRs.

@cpitclaudel

Copy link
Copy Markdown

Could this PR be causing #14397?

@jeremyn

jeremyn commented Jan 23, 2018

Copy link
Copy Markdown
Contributor

I've added a comment at #14397 (comment).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants