From: Jan Hudec <bulb@ucw.cz>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Andy Parkins <andyparkins@gmail.com>,
git@vger.kernel.org, Pavel Roskin <proski@gnu.org>
Subject: Re: [RFH] QGit: how to cram a patch in a crowded screen
Date: Mon, 4 Jun 2007 17:41:19 +0200 [thread overview]
Message-ID: <20070604154119.GA3299@efreet.light.src> (raw)
In-Reply-To: <e5bfff550706020437i3f54d459rdbe9070fe03a28c9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
On Sat, Jun 02, 2007 at 13:37:03 +0200, Marco Costalba wrote:
> 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>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-04 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 8:46 [RFH] QGit: how to cram a patch in a crowded screen Marco Costalba
2007-05-26 9:34 ` Andy Parkins
2007-05-26 20:44 ` Marco Costalba
2007-05-27 15:38 ` Jan Hudec
2007-05-27 15:56 ` Marco Costalba
2007-05-31 19:56 ` Jan Hudec
2007-06-02 11:37 ` Marco Costalba
2007-06-04 15:41 ` Jan Hudec [this message]
2007-05-30 13:08 ` Andy Parkins
2007-05-30 18:18 ` Marco Costalba
2007-05-31 0:23 ` Pavel Roskin
2007-05-31 4:39 ` Marco Costalba
2007-05-31 9:27 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070604154119.GA3299@efreet.light.src \
--to=bulb@ucw.cz \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.com \
--cc=proski@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.