Some useful commands to find commits using Git: Filter by content

Filter by the contents of a commit. Think of it as if you do a git log -p (shows the diff of each commit) and then you search the output.

git log -S var_dump

Filter by commit message

git log --grep "FRB-666"

Filter by author

git log --author "Arturo"

You can use emails and several values:

git log --author "outlook.com|hotmail.com"

Filter by date

Conveniently accepts --before and --after

git log --before "2017-06-11"

Git log format

I've found that git log is powerful, but sometimes difficult to read. Normally I use this git alias to show a nice tree in the console:

$ git config --global alias.lg
log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit

This will show a tree like this when you type git lg

I started having some issues when using git inside a Linux VM while setting up an experimental Drupal development environment. I wasn't able to clone repositories because I was getting some errors saying the remote host hanged unexpectedly, or couldn't push changes. However I was able to clone shallow repos, but strangely Bitbucket and Gitlab seemed to be more prone to these errors.

$ git clone git@....
Cloning into 'somedir'...
error: RPC failed; curl 56 GnuTLS recv error (-12): A TLS fatal alert has been received.
fatal: The remote end hung up unexpectedly

At some point, disabling offloading solved the issue: Disabling Offloading on Ubuntu 18.04 with Netplan and/or systemd-networkd

It apparently worked, but soon I found that only worked when using Github. Of course, that didn't make any sense. When I tried to push changes to Bitbucket or Gitlab I had again the same strange errors saying the remote host hung up unexpectedly.

I tried to debug git using GIT_SSH_COMMAND, tried using https and even recompiled git to use OpenSSL instead of GnuTLS. Nothing seemed to work... Until I found an answer from this guy who found the solution): I needed to update my Wi-Fi drivers.

Strange error indeed.

TLDR: A bug between Hyper-V and my Wi-Fi card (Intel 5060) was causing this. Updating the drivers solved it:

https://downloadcenter.intel.com/download/28876/Windows-10-Wi-Fi-Drivers-for-Intel-Wireless-Adapters?v=t