All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: skimo@liacs.nl
Cc: Paul Mackerras <paulus@samba.org>, git <git@vger.kernel.org>
Subject: Re: [PATCH] gitk: Add "Refs" menu
Date: Wed, 12 Oct 2005 10:34:52 -0400	[thread overview]
Message-ID: <1129127692.31997.10.camel@dv> (raw)
In-Reply-To: <20051012073139.GV8383MdfPADPa@greensroom.kotnet.org>

On Wed, 2005-10-12 at 09:31 +0200, Sven Verdoolaege wrote:
> On Tue, Oct 11, 2005 at 09:26:20PM -0400, Pavel Roskin wrote:
> > Browsing trees and opening files for a given commit would be great and
> > helpful from developers migrating from CVS.
> 
> Something like this ?
> 
>     From: Ingo Bormuth <ibormuth@efil.de>
>     To: git@vger.kernel.org
>     Cc: paulus@samba.org
>     Subject: [PATCH] Gitk tree view (correction)
>     Message-ID: <20050824223550.GA23693@kruemel>

That's pretty good, thank you.  Although I think "Tree" and "Commit"
should be links on top of the view pane rather than a button.  "Commit"
button is especially confusing - one could think that it would commit
something.

Also, it would be really great to put line numbers in a separate widget
so that they are never selected with the text.  When done correctly,
most users will never want to turn the line numbers off.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2005-10-12 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06  0:38 [PATCH] gitk: Add "Refs" menu Pavel Roskin
2005-10-06  4:11 ` [PATCH] gitk: Add "Refs" menu - revised Pavel Roskin
2005-10-11 12:17 ` [PATCH] gitk: Add "Refs" menu Paul Mackerras
2005-10-12  1:26   ` Pavel Roskin
2005-10-12  7:31     ` Sven Verdoolaege
2005-10-12 14:34       ` Pavel Roskin [this message]
2005-10-12 11:55     ` Marco Costalba
2005-10-12 16:03       ` Pavel Roskin
2005-10-12 17:47       ` H. Peter Anvin

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=1129127692.31997.10.camel@dv \
    --to=proski@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=skimo@liacs.nl \
    /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.