git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Junio Hamano <gitster@pobox.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Marco Costalba <mcostalba@gmail.com>
Subject: Re: [RFC] git-blame and git-gui blame wishlist
Date: Mon, 3 Sep 2007 23:25:50 -0400	[thread overview]
Message-ID: <20070904032550.GT18160@spearce.org> (raw)
In-Reply-To: <200709031240.04235.jnareb@gmail.com>

Jakub Narebski <jnareb@gmail.com> wrote:
> 1. In git-gui blame viewer you can click on shortened sha1 of a commit
...
> 2. Sometimes I'm interested only in part of a file. Thus I'd like
...
> 3. Sometimes when reviewing patches I do wonder: why the preimage looks
...

I've seen this list before... hmm, yea, I have, right here:

	From: Jakub Narebski <jnareb@gmail.com>
	To: git@vger.kernel.org
	Subject: git-blame and blame GUI wishlist
	Date: Mon, 6 Aug 2007 00:09:37 +0200
	Message-Id: <200708060009.37595.jnareb@gmail.com>

;-)

To the extent that I can get around to it, it has been on my todo
list.  But you have to keep in mind that my todo list for git is
very, very, very long and my time to work on it is quite limited
in comparsion.

I certainly would not mind if more folks helped out on git-gui by
contributing patches to it.  :)

Unfortunately the survey results seem to indicate that not many of
our users know Tcl/Tk.  Yea, it is a somewhat weird language, but
there's books and other documentation available for free through
a series tubes that Mr. Gore invented.  Most programmers can pick
up Tcl.  They just might want to hurt themselves afterwards...

-- 
Shawn.

           reply	other threads:[~2007-09-04  3:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200709031240.04235.jnareb@gmail.com>]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070904032550.GT18160@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=mcostalba@gmail.com \
    --cc=torvalds@linux-foundation.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).