I often need to look around by using git status, git diff <branch>, git diff <commit> and git show.\r +
pijul patch <hash> already does something in this direction, but it is binary and I don't know how to print it nicely as e.g. here on nest:\r+
my < and > characters were are lost in the comment…\r +
So here again:\r +
I often need to look around by using git status, git diff BRANCH, git diff COMMIT and git show COMMIT.\r +
pijul patch PATCH already does something in this direction, but it is binary and I don't know how to print it nicely as e.g. here on nest: https://nest.pijul.com/pijul_org/pijul/patches/AbTgXJ2pBNM_0HlCrLoBauoAzoYK0L3Pbd801149T45zInQAYo2Rl787yf8ovkdKfLinv3F-UAMpLS8UERdZPCY\r+
Since there is no +1 button here (yet?), I'll also express my desire for this future here.\r +
I'd really like to try out pijul, but its hard to take some of it's best features like cherry-picking when there is not really a accessible way to see what you are cherry-picking.
*future -> feature\r +
*take advantage of some of its best features
This is very true indeed. I hope we will be able to implement that soon.