One thing I can't quite get right with `b4 shazam -S/H` is how to tell it to just use top of tree and NOT whatever it finds as the right base commit. Working around this with just going back to patchwork bundle and pasting in the cover letter on merging a branch.
@monsieuricon I don't have that as an option for shazam or am, and I just did a pip install b4 to make sure I was up to date.
@monsieuricon So here's where things are even more fun. "pip show b4" says 0.13.0, "b4 --version" says 0.12.4 and b4 shazam --help doesn't show the option.
@monsieuricon Well, this doesn't make a ton of sense. "which b4" says the venv one. The venv one has 0.13.0 as the version (the one in my homedir is 0.12.4). Updating my non-venv b4 version to 0.13.0 means that now, yes, I'm really getting the right b4. Even if my PATH says it should have been using the venv one before my local pip one. Sigh. Thanks!