You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Wouldn't it be better to keep historical versions in branches rather than in master ?
Have a look at my fork. I have created a few branches with one dupinator.py and one README.md in each. Each branch is used to keep an historical version.
However, it seems you will have to create these branches if you like the idea and want to merge my changes.
By the way, I have also created a branch to publish my dupinator.py which I have used for a few years.
I think it goes a long way in implementing your 'TODO : Create better rules to find "original"'
I'm considering merging all the features from your master and my version. There are also a few good ideas in the discussion here : http://code.activestate.com/recipes/362459/
Regards,
The text was updated successfully, but these errors were encountered:
Hi,
Wouldn't it be better to keep historical versions in branches rather than in master ?
Have a look at my fork. I have created a few branches with one dupinator.py and one README.md in each. Each branch is used to keep an historical version.
However, it seems you will have to create these branches if you like the idea and want to merge my changes.
By the way, I have also created a branch to publish my dupinator.py which I have used for a few years.
I think it goes a long way in implementing your 'TODO : Create better rules to find "original"'
I'm considering merging all the features from your master and my version. There are also a few good ideas in the discussion here : http://code.activestate.com/recipes/362459/
Regards,
The text was updated successfully, but these errors were encountered: