Hi, Arjen, On Jan 30, 2015, at 1:15 AM, Arjen Markus wrote:
> the thing that has frustrated me using git is the fact that unlike subversion > and most other revision control systems I have used, things are arranged in > small steps. This is a difference, to be sure, but I have grown to appreciate that git provides more fine grained control. > For instance: “git fetch” only fetches the changes into the local repository, > it does not change the checked-out files. That happens in the “git merge” > step. Isn't that great! :-) I generally prefer to fetch and merge in two distinct steps so I can examine the newly fetched changes before merging them. That's harder to so with svn (lots of rdiff and rlog). > (there is also the matter of explicitly adding files to the commit step – > another difference with subversion). I first thought that was a weird and annoying extra step, but I have grown fond of this capability as well. I often find myself with several files to commit, yet the changes are not all related. Git makes it easy to commit only some of my modified files, so I can make each commit contain just the changes that I want to group together. There's even "git add -p" which lets you pick and choose which changes within files should be added to the commit. Talk about fine grained control! Dave ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
