> > Well, as you have noticed in Java, C or C++, switching branches does >> not call make automatically :) >> >> You can use git hooks for that. >> > > Ok. Then I would suggest you take the code source of CLANG, LLVM, > OpenOffice or of the Linux kernel, you add the git hooks to call make, and > you admire how fast changing branches becomes ;)
Sure; large project would take long regardless but comparatively small (~10kloc) project would get checkouted fast, also it doesn't just completely rewrite the filesystem, but only the actual changes (which is for my use cases most of the time in the order of tens of files) > Want to switch branches before committing? Can do. > How? :-o If I switch the branch from git (command line) then there is disparity. I'm not a git expert, but I know enough about git (and git users:)) that > each and everyone may have its opinion on the way git should be used, and, > as such, I've decided on GitFileTree that I wouldn't claim to hold the way > it should be used™. Yes, I need to think about myself a bit... I am used to certain workflow and I guess I was greedy with wanting everything. > I will have to think about it. I am used to my git workflow and now I am >> kind of lost how to use it properly from Pharo; since I am cut off from >> git. One idea that is crossing my mind is having synchronized filedumps >> (filetree) in a folder and not worry about git or monticello inside >> Pharo at all. (And when I change code outside it would magically change >> also inside). >> > > Please explore the idea; just try to focus on that: > Adding it my (endless) todolist, I would need to learn a bit (=lot) about monticello first and how these things actually work inside Pharo so it could be done, but just like everybody I have a lot on my plate. (And I have also tend to eat more than I can chew.) > > At the same time, there is just me and Max (and Esteban as well, I think) > working on getting that git support working, so don't bash us too much. > It's hard enough to get it done (look at Max questions about libcgit) that > we don't need too much additional pressure. I am really sorry if my message sounded harsh, I in no way intended something like that. Sometimes I am more greedy and picky about software than I should be. I'll add some positive emoticons next time so it will be more happy. :) I am grateful for the work you have done, after all I do like it and I am happy I was able to make the switch to git, despite me missing features; so please don't my ramblings as bashing, they were intended (albeit bit directly) only as questions/ideas. Peter
