Rick Umali

Author
+ Follow
since Dec 31, 2003
Rick likes ...
Linux Python VI Editor
Husband and father.
High-tech worker.
Author of "Learn Git in a Month of Lunches" (Manning Publications).
Greater Boston, MA
Cows and Likes
Cows
Total received
5
In last 30 days
0
Total given
0
Likes
Total received
2
Received in last 30 days
0
Total given
68
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Rick Umali

Hello Peggy, I hope you have a good promotion for your book!
4 months ago
Hello Ben! I hope your book does well. Regular expressions are everywhere, and a valuable and indispensable tool for anyone working in computers.
7 months ago
Hi Bryson, Good luck with the book promotion! I'm a big fan of beginner books.
1 year ago
Welcome to the forums, William!
2 years ago
Hello Yakov Fain and Anton Moiseev. I have enjoyed reading your book while it was in MEAP!

Enjoy your time on the forums!
Welcome Jonathan, and Good Luck with the book promotion!
2 years ago
I like the snappy dialogue and funny names throughout your book (I downloaded the sample from NoStarch)! I like the hard-boiled style. What crime/detective novels inspired you when writing the book. Thank you!
2 years ago
Congratulations on the book, Mr. Kubica! I skimmed the first few pages, and it seems quite engaging!
2 years ago
Hi Andreas and Michael! Welcome to the forum, and I hope you enjoy promoting the book here!
3 years ago
Thank you, Henry, and thank you to everyone who contributed to the threads. I enjoyed being here! Thank you again!
My only opinion is that git pull --rebase would probably be "more advanced" for the first time user of Git. In the book, I emphasize that git pull is really git fetch + git merge. With the --rebase switch, git pull uses git rebase, instead of git merge, which sort of brings us back to the top of our thread (rebase v. merge)!
Git can handle binary files (such as spreadsheets, MS Word files, and image files). It would not be hard to pull up previous versions of a spreadsheet, for example, but comparing it to the current version is tricky because Git relies on third-party tools for displaying the differences. I'm not aware of any third-party tools for displaying the difference between two spreadsheets, but if one did exist, you could configure Git to use that tool. (Git for Windows sets up the third-party tool antiword for taking the difference between MS Word files.)

As for having a non-technical team set up SSH keys to commit work, I'd say that would be hard. GitHub supports username/password authentication, and this could be used at the start.
I reviewed the Git/SVN comparison page on the Git Wiki:

https://git.wiki.kernel.org/index.php/GitSvnComparison

The author, Shawn Pearce, points out some advantages SVN has over Git:

1) You can retrieve parts of an SVN repository. With Git, you cannot obtain "part" of a repository (though you can clone up to a certain depth).

2) SVN has predictable revision numbers. Git, on the other hand, has SHA1 IDs for its commit IDs.

A small list, to be sure. I hope others chime in with more.