Re: [PATCHv2] gitk: Replace next and prev buttons with down and up arrows.

2014-01-23 Thread Paul Mackerras
On Wed, Jan 22, 2014 at 12:18:27PM -0800, Junio C Hamano wrote: Is this a good time for me to pull from you? I see these on your 'master' branch. 8f86339 gitk: Comply with XDG base directory specification 786f15c gitk: Replace next and prev buttons with down and up arrows

Re: [PATCHv2] gitk: Replace next and prev buttons with down and up arrows.

2014-01-23 Thread Junio C Hamano
Paul Mackerras pau...@samba.org writes: Yes, please pull. I have just pushed one more: 76d64ca gitk: Indent word-wrapped lines in commit display header Thanks. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More

Re: [PATCHv2] gitk: Replace next and prev buttons with down and up arrows.

2014-01-22 Thread Paul Mackerras
On Tue, Jan 21, 2014 at 10:33:02AM -0500, Marc Branchaud wrote: On 13-12-18 11:04 AM, Marc Branchaud wrote: Users often find that next and prev do the opposite of what they expect. For example, next moves to the next match down the list, but that is almost always backwards in time.

Re: [PATCHv2] gitk: Replace next and prev buttons with down and up arrows.

2014-01-22 Thread Junio C Hamano
Paul Mackerras pau...@samba.org writes: On Tue, Jan 21, 2014 at 10:33:02AM -0500, Marc Branchaud wrote: On 13-12-18 11:04 AM, Marc Branchaud wrote: Users often find that next and prev do the opposite of what they expect. For example, next moves to the next match down the list, but that

Re: [PATCHv2] gitk: Replace next and prev buttons with down and up arrows.

2014-01-21 Thread Marc Branchaud
On 13-12-18 11:04 AM, Marc Branchaud wrote: Users often find that next and prev do the opposite of what they expect. For example, next moves to the next match down the list, but that is almost always backwards in time. Replacing the text with arrows makes it clear where the buttons will take

[PATCHv2] gitk: Replace next and prev buttons with down and up arrows.

2013-12-18 Thread Marc Branchaud
Users often find that next and prev do the opposite of what they expect. For example, next moves to the next match down the list, but that is almost always backwards in time. Replacing the text with arrows makes it clear where the buttons will take the user. Signed-off-by: Marc Branchaud