Re: [Cake] Cake tree unreadable

Sebastian Moeller writes: > Hi All, > > >> On Nov 28, 2017, at 23:37, Dave Taht wrote: >> >> >> A flag day here is feasible. I will fiddle along the lines you describe. >> >> As for other flag days... >> >> I'm toying with the idea of fixing xstats in a

Re: [Cake] Cake tree unreadable

Hi All, > On Nov 28, 2017, at 23:37, Dave Taht wrote: > > > A flag day here is feasible. I will fiddle along the lines you describe. > > As for other flag days... > > I'm toying with the idea of fixing xstats in a separate branch. I really > hate the idea of breaking backward

Re: [Cake] Cake tree unreadable

Dave Taht writes: > A flag day here is feasible. I will fiddle along the lines you > describe. FWIW I don't think the history is that bad. Sure, there are a bunch of merge commits, but picking out the real ones is not that difficult (unless you are using the github web interface,

Re: [Cake] Cake tree unreadable

A flag day here is feasible. I will fiddle along the lines you describe. As for other flag days... I'm toying with the idea of fixing xstats in a separate branch. I really hate the idea of breaking backward compatability here, but I do suspect it will be a barrier to upstreaming, and it is,

Re: [Cake] Cake tree unreadable

> On 28 Nov 2017, at 18:48, Dave Taht wrote: > > > > It sounds like your git-foo is stronger than ours! I'm not even trying > to get head to work, tho my intent would be to promote cobalt to it. git checkout master git pull (does the equivalent of git fetch origin; git