Hi, I'm considering switching to git as an SCM system. I often find myself on the train with my laptop, wanting to work on nbd, but being hampered in that by the fact that I can't work with the repository while offline. Additionally, git's ability to remember what has been merged and what hasn't been, should help me keep track of what patches that should be applied across all versions of nbd have been so applied, and which haven't been. There have been problems in the past where a new .0 release still had some bugs in it that had already been fixed in the past on the old branch, which is kindof embarrasing; I hope to be able to avoid that in the future by proper merging.
Thoughts? Having said that, I should note that currently, I'm a git newbie; I read the tutorial yesterday, and am playing with it a bit now, but I still have a lot to learn. Before this switch will happen, I'll obviously have to understand quite a bit more about how the git system works... -- <Lo-lan-do> Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Nbd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nbd-general
