pijul_org / pijul

#10 print diff

Opened by pothos, on March 20, 2017
Closed
pothos commented on March 20, 2017

I often need to look around by using git status, git diff <branch>, git diff <commit> and git show.\r + \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+ https://nest.pijul.com/pijul_org/pijul/patches/AbTgXJ2pBNM_0HlCrLoBauoAzoYK0L3Pbd801149T45zInQAYo2Rl787yf8ovkdKfLinv3F-UAMpLS8UERdZPCY\r +

pothos commented on March 20, 2017

my < and > characters were are lost in the comment…\r + \r + So here again:\r + \r + I often need to look around by using git status, git diff BRANCH, git diff COMMIT and git show COMMIT.\r + \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+

hobofan commented on March 27, 2017

Since there is no +1 button here (yet?), I'll also express my desire for this future here.\r + \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.

hobofan commented on March 27, 2017

*future -> feature\r + *take advantage of some of its best features

lthms commented on June 3, 2017

This is very true indeed. I hope we will be able to implement that soon.