From: Ingo Molnar <mingo@elte.hu>
Date: Sun, 19 Jun 2005 13:00:35 GMT
Subject: Re: qgit-0.6
Message-ID: <20050619130035.GA15355@elte.hu>
In-Reply-To: <20050618103805.8461.qmail@web26302.mail.ukl.yahoo.com>


* Marco Costalba <mcostalba@yahoo.it> wrote:

> A word on annotate: In file viewer, after a while :-), the file 
> contents will change to show the annotations. Annotations are 
> calculated in background so it may takes some time to show (it depends 
> mostly on fetching history patches with git-diff-tree -p ). History is 
> snapshotted to actual loaded data so peraphs you need qgit to have 
> loaded an interesting amount of data before calling file viewer.

works fine here and is nice and fast, but there are a few minor visual 
glitches:

- annotated file contents are not properly aligned over each other. E.g.  
  check commit 7875b50d1a9928e683299b283bfe94778b6c344e in the current 
  git repository, and select read-tree.c and view it annotated - the 
  lines start right after the author field ends, not in any aligned way.

- the tree visualization is hard to follow - gitk's output is much 
  nicer. As an example of nice rendering check out the octopus merge 
  around commit 211232bae64bcc60bbf5d1b5e5b2344c22ed767e. One glance at 
  the gitk output shows what happened - qgit's output is in essence 
  unreadable.

and a few requests for enhancements if you dont mind:

 - in annotated mode, it would be nice to select a particular line 
   and then double-click would jump to the commit that added that line.  
   This would nicely round up annotation support.

 - plaintext search capability in every window. E.g. in the annotated
   file window i often would like to search for some code, or to jump to
   a given line.

	Ingo