-
Notifications
You must be signed in to change notification settings - Fork 11
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.
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
Proposal for a TripStatusGroup #38
Conversation
@skinkie, this pull request is apparently based on master, right? Could you base it on v1.1 instead? |
Why was this "Proposal" merged to master instead of changes_for_v1.1? :( |
@sgrossberndt you can revert it if you want... |
Should have been in v1.1, have a better commit message and as I know you should not do it, but nevertheless I propose to force push to master to remove both commits (and open a pull request for What is your opinion on this, @skinkie , @pvgrumbkow , @herlitze , @ue71603 ? |
Option A sounds easier if it done correctly. |
Done: 471ce64 |
* Proposal for a TripStatusGroup (#38) * Change "Unable" to "Infeasible" Co-authored-by: Stefan de Konink <stefan@konink.de>
No description provided.