Skip to content
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

Branches for historical versions #1

Open
e-hamon opened this issue Oct 8, 2015 · 1 comment
Open

Branches for historical versions #1

e-hamon opened this issue Oct 8, 2015 · 1 comment

Comments

@e-hamon
Copy link

e-hamon commented Oct 8, 2015

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,

@jvhaarst
Copy link
Owner

jvhaarst commented Oct 9, 2015

I'll have a look somewhere next week, I really haven't looked at this for a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants