kubernetes-retired/kube-mesos-framework

Reset history

Closed this issue · 7 comments

I think we should consider resetting the history on this project. We started as a straight clone to ease the transition, but now that we've transitioned to a more permanent structure, there isn't a whole lot of benefit to keeping history on all of vendor as a for instance.

Keeping the old history is hiding the real actors in this repo from people searching through.

@k82cn, what do you think?

can you filter-branch out nearly everything?

can you filter-branch out nearly everything?

The only way I know to do that is to start over from kube/kube. Knowing the end state I could use filter-branch --subdirectory-filter and then copy th ecurrent state of the repo over and force push.

Is there a cleaner way?

Not that I know of.

On Wed, Sep 28, 2016 at 4:13 PM David Eads notifications@github.com wrote:

can you filter-branch out nearly everything?

The only way I know to do that is to start over from kube/kube. Knowing
the end state I could use filter-branch --subdirectory-filter and then copy
th ecurrent state of the repo over and force push.

Is there a cleaner way?


You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#21 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACDCFHDu1S0j_8xH_489WCHi3iRuDNMks5quvSCgaJpZM4KJSPe
.

@k82cn I'm inclined to do this tomorrow to help with the ability to inspect the project. I'll save history on stuff from contrib/mesos In case something goes wrong: current head is b4a9380

k82cn commented

Agree with you to clear up the history :). Thanks very much.

Alright, here goes. There's no way to do this other than a force push. I've created a branch here: https://github.com/kubernetes-incubator/kube-mesos-framework/tree/unfiltered-history which I think will survive the push, but which we should remove when we're sure we're happy with the new history.

I think it worked and the result looks a lot cleaner.