[PATCHv3 0/3]More diffs for commit/status

2015-03-05 Thread Michael J Gruber
v3 has the following changes: - new leading patch by Junio to clean up t7508 (slightly modified by myself) - adjust tests accordingly - revert back to standard c/,i/ resp. i/,w/ diff prefixes with a header line Open questionis for 3/3: - Do we need the header to stick out even more? (I don't think

Re: [PATCHv3 0/3]More diffs for commit/status

2015-03-05 Thread Junio C Hamano
Michael J Gruber writes: > v3 has the following changes: > - new leading patch by Junio to clean up t7508 (slightly modified by myself) > - adjust tests accordingly > - revert back to standard c/,i/ resp. i/,w/ diff prefixes with a header line > > Open questionis for 3/3: > - Do we need the heade

Re: [PATCHv3 0/3]More diffs for commit/status

2015-03-05 Thread Junio C Hamano
Junio C Hamano writes: > Michael J Gruber writes: > >> - Do we want the header line also for "status -v"? (I would say yes, but that >> would be a change to current behaviour.) > > I would not object to it very strongly, but I do not see a point in > changing the behaviour. > > And I do not se

Re: [PATCHv3 0/3]More diffs for commit/status

2015-03-05 Thread Junio C Hamano
Junio C Hamano writes: > Extending this line of thought further. > > If I am reading your patch 3/3 right, "status -v -v" shows the > header when there are patches to be shown for the category. I am > not sure if that is the most helpful way for the users, when either > c/i xor i/w diffs is mis