git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFH] QGit: how to cram a patch in a crowded screen

From
JHJan Hudec <bulb@ucw.cz>
Date
Jun 4, 2007, 15:41 UTC
Message-ID
<20070604154119.GA3299@efreet.light.src>
In-Reply-To
<e5bfff550706020437i3f54d459rdbe9070fe03a28c9@mail.gmail.com>
On Sat, Jun 02, 2007 at 13:37:03 +0200, Marco Costalba wrote:
Show 12 quoted lines
> On 5/31/07, Jan Hudec <bulb@ucw.cz> wrote:
> >
> >I have to say that I like the gitk way better. There is the issue of
> >over-scrolling. I often want to quickly scan through the diff, so I scroll
> >pretty quickly and it switches over when I reach the end.
> >
> 
> Ok. "Smart Browsing" ;-)  patch series pushed to qgit4.
> 
> Refer to patches logs for a little documentation.
> 
> Please give feedback if this patch series it's not smart enough for you.

I think it feels quite good. And leaves room for additional pages. Ie. merge could have the "interesting" (--cc) diff and diff against each parent in turn.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>
Previous: Marco CostalbaNext: Andy Parkins
Message 8 of 13 in “[RFH] QGit: how to cram a patch in a crowded screen”
  1. Marco CostalbaMay 26, 2007
  2. Andy ParkinsMay 26, 2007
  3. Marco CostalbaMay 26, 2007
  4. Jan HudecMay 27, 2007
  5. Marco CostalbaMay 27, 2007
  6. Jan HudecMay 31, 2007
  7. Marco CostalbaJun 2, 2007
  8. Jan HudecJun 4, 2007
  9. Andy ParkinsMay 30, 2007
  10. Marco CostalbaMay 30, 2007
  11. Pavel RoskinMay 31, 2007
  12. Marco CostalbaMay 31, 2007
  13. Alex RiesenMay 31, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.