Skip to content

Conversation

@pganssle
Copy link
Member

@pganssle pganssle commented Jan 3, 2018

Closes #339 in favor of #565 and #593.

@Cheukting I had to make a new branch to clean up your git history, which wouldn't have merged cleanly into the master branch as it was. If you make further PRs, it would probably be advisable to delete your fork and make a new one, because I think the master branch is out of sync with the master branch here.

@pganssle pganssle added this to the 2.7.0 milestone Jan 3, 2018
@Cheukting
Copy link
Contributor

Yes it was a nightmare as I worked on the master branch. Thanks for tidy it up eventually and I hope my work helps (not causing too much trouble).

Definitely started a new fork when you have taken over and after make sure that deleting my fork will not delete the edit done.

@pganssle
Copy link
Member Author

pganssle commented Jan 4, 2018

Only problem is a dead link, merging.

@pganssle pganssle merged commit 888e18d into dateutil:master Jan 4, 2018
@pganssle pganssle mentioned this pull request Mar 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants