search

ucsd-progsys / liquid-fixpoint

Horn Clause Constraint Solving for Liquid Types
BSD 3-Clause "New" or "Revised" License
139 stars 61 forks source link

Should we clean up old branches? #108

Closed BenjaminCosman closed 9 years ago

BenjaminCosman commented 9 years ago

There are 17 of them. At the very least, should we remove some of the following branches that have been fully merged into master?

bitvector cores list_parsing smt-refactor sorts stats tmp_fix1

(same goes even more so for liquidhaskell - 29 branches, with fully merged:

cores cutsolver ghc-7.10 non_applied_tycons paths pprinting sorts test-liquid-opts tiny-travis-fix travis_retry type-class

)

christetreault commented 9 years ago

I can delete the cores branches. I was holding onto them "in case I need them", but I suppose that's just silly...

ranjitjhala commented 9 years ago

I have the same fear but best to delete after merging with master :)

On Aug 31, 2015, at 4:02 PM, Chris Tetreault notifications@github.com wrote:

I can delete the cores branches. I was holding onto them "in case I need them", but I suppose that's just silly...

— Reply to this email directly or view it on GitHub.

gridaphobe commented 9 years ago

If a branch has been fully merged and you're done with it, you might as well delete it. No information will be lost..

ranjitjhala commented 9 years ago

Yes (delete them) thanks!

BenjaminCosman commented 9 years ago

Done