Title
#core
a

alessandrogario

12/03/2018, 5:34 PM
It seems like it's been developed in a private branch that is not visible; we recently started tracking the changes in the whole Buck project and it would be nice to follow development
fmanco

fmanco

12/03/2018, 5:42 PM
I'm working on preparing the commit(s). I'll try to break it down as much as I can but it's proving very hard to do. However this is going to be the only aggregated commit we're doing. After this will start committing everything as single commits.
a

alessandrogario

12/03/2018, 5:45 PM
While it would be nice to refactor the current 2 available commits on experimental to make it easier to everyone to rebase their branches, I was talking about the next commit(s) that will add Windows support. As I have already went through nearly all of the new Buck files that have been introduced, it would be nice to have incremental changes at least from now on if it's not too troublesome
fmanco

fmanco

12/04/2018, 1:57 PM
Oh I see, I prefer to have "clean" commits on experimental branch (which will become master eventually) but to make your life easier I can push another branch temporarily with current commits plus another commit for the windows changes that will be integrated now on experimental, so that you'll at least be able to see what changed since. Would that help?
a

alessandrogario

12/04/2018, 3:12 PM
Yes! if it is possible, I'd appreciate it! Thanks!
fmanco

fmanco

12/07/2018, 5:31 PM
I pushed a branch called temporary that contains an incremental commit on top of the previous 2 commits on experimental. I'll remove this eventually but no rush. Let me know once you're done with it.