|
[Sponsors] |
November 23, 2009, 14:17 |
GIT history OF 1.5 to 1.6
|
#1 |
New Member
Jacques
Join Date: Oct 2009
Posts: 15
Rep Power: 16 |
Hello,
I was wondering if there is any way of having a continuous GIT history of changes from 1.5.x to 1.6.x ? When I checkout the git for 1.6.x and look at the history it only goes back to 07/2009, I assume that there have been massive changes between the last 1.5.x patch and the first 1.6.x ... Thanks anyone, Jacques |
|
November 24, 2009, 03:24 |
|
#2 | |
Senior Member
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,684
Rep Power: 40 |
Quote:
|
||
November 24, 2009, 05:45 |
How ?
|
#3 |
New Member
Jacques
Join Date: Oct 2009
Posts: 15
Rep Power: 16 |
Thank you Olesen,
could you indicate the procedure for this ? It would be very helpful, as I am not a git guru. Cheers, J. |
|
November 25, 2009, 02:28 |
|
#4 | |
Senior Member
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,684
Rep Power: 40 |
Quote:
Instead of squeezing it all in here, I made a blog entry about it instead: http://olesenm.github.com/2009/11/24...FOAM-versions/ |
||
November 25, 2009, 04:35 |
Thanks!
|
#5 |
New Member
Jacques
Join Date: Oct 2009
Posts: 15
Rep Power: 16 |
Thank you for your very well thought out post.
I will try it out. It is a bit frustrating not to have the complete history of changes. I would be interested in seeing the commit messages for example. It would also give a better idea of what groups of code were modified together / at the same time.. etc.. . Thanks again, J. |
|
November 25, 2009, 04:55 |
|
#6 | |
Senior Member
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,684
Rep Power: 40 |
Quote:
Other people prefer a fair number of smaller commits - I tend to work like that at times. After a particular feature (eg, a class method) has reached a somewhat stable stage I commit those portions of the code. I use this as a safety net in case I need to go back to an particular stable version later. Reworking a particular class might then result in 10 or more separate commits before it is all done. In between there might be some other commits that are fully unrelated. In both cases you might not easily find the groups of changed code immediately. |
||
December 11, 2009, 19:09 |
|
#7 | |
Member
Maxim Loginov
Join Date: Mar 2009
Posts: 33
Rep Power: 17 |
Quote:
Code:
git diff foam15x/master foam16x/master |
||
December 12, 2009, 08:22 |
|
#8 |
Senior Member
Mark Olesen
Join Date: Mar 2009
Location: https://olesenm.github.io/
Posts: 1,684
Rep Power: 40 |
Nope, you didn't miss anything. The merge 'ours' approach is, in this case, primarily useful if you want a single repository later with all of the 1.5.x and 1.6.x changes. However, if you have some of your own custom changes that you would like to rebase onto 1.6.x, this type of approach can help there.
|
|
May 1, 2010, 04:16 |
|
#10 |
New Member
Jacques
Join Date: Oct 2009
Posts: 15
Rep Power: 16 |
Using cmake is a nice idea... Can you tell me if freefoam is currently maintained ? (It seems like the last commit was done in January, and only Michael Wild seems to be developing..)
|
|
May 1, 2010, 04:48 |
|
#11 |
Member
Maxim Loginov
Join Date: Mar 2009
Posts: 33
Rep Power: 17 |
||
December 25, 2013, 22:40 |
|
#12 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,974
Blog Entries: 45
Rep Power: 128 |
Greetings to all!
I know that this thread is now really old, but is still the best place to report this - If anyone is looking for a single repository that has the (nearly) complete git history of OpenFOAM 1.5.x to 2.2.x, check this repository: https://github.com/wyldckat/OpenFOAM-combo/ It's not perfectly complete, because I used a lot of "git rebase", which condenses the commits to the minimum necessary, which leads to a more simplified commit history. This also means that the git hashes are not preserved using this technique, while Mark Olesen's technique does preserve the original hashes. The "README.md" file should have almost all of the necessary information to reproduce the same thing. Best regards, Bruno
__________________
|
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
1.5 => 1.6: Matrix template - ODETest does not compile | markc | OpenFOAM Programming & Development | 2 | November 26, 2013 17:00 |
Change in triangle::intersection breaks stitchMesh in 1.5 and 1.6 | gschaider | OpenFOAM Bugs | 7 | February 12, 2010 09:21 |
ChtMuliRegionFoam-Case (OF 1.6 Tutorial-case -> OF 1.5) | suitup | OpenFOAM | 15 | November 11, 2009 12:43 |
OpenFOAM Patched Version 1.5 via git Repository | OpenFOAM discussion board administrator | OpenFOAM Announcements from ESI-OpenCFD | 0 | August 26, 2008 05:06 |
CFX4.3 -build analysis form | Chie Min | CFX | 5 | July 12, 2001 23:19 |