Chris Siebenmann
@b0rk I voted command line + GUI, with the latter being for my Magit usage (and I guess Github blame view). I use the command line for pull, rebase, log, diff, and many blame operations. I use Magit for committing things, especially selective commits, and thus for checking diffs before I commit and so on. (And some use of git-timemachine in Emacs to move back and forth through the history of a file to track things.)
But my git use is odd since I track and monitor a lot of upstream repos.
Account: Computers
Author
Chris Siebenmann
@pro @anime @b0rk The Github blame view has two killer features for me for picking through the history of changes to something: it gives me immediate access to the commit and especially a 'git blame' view of the file as it was just prior to that change. The latter is extremely compelling for jumping back through the history of a function or a constant or etc (which I do a lot as I try to understand something in other people's software).
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.