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: Sun, 27 May 2007 17:38:52 +0200 [thread overview]
Message-ID: <20070527153852.GA30365@efreet.light.src> (raw)
In-Reply-To: <e5bfff550705261344l604543e7h64c20c1fc0979f20@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On Sat, May 26, 2007 at 22:44:28 +0200, Marco Costalba wrote:
> On 5/26/07, Andy Parkins <andyparkins@gmail.com> wrote:
> >
> >For example, the log view widget would show:
> >
> ><Header>
> ><Log Message>
> ><Patch>
> >
> >All visually distinct to improve searching by eye (perhaps including
> >clear separators between files patched). Then the file list could
> >include a "<header>" psuedo-file that would jump back to the top of the
> >viewer.
>
> This seems really gitk like. Not that I don' t like it, but _if_ it's
> possible I would prefer something a little bit more original.
IMHO there's no point in being original. The gitk way works well, because it
requires only one action -- scrolling -- throughout reading of the whole
commit (description + patch). With any kind of tabs, there's always an extra
action for switching.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-27 15:39 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 [this message]
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
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=20070527153852.GA30365@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.