public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha•warpmail.net>
To: Jesse van den Kieboom <jesse@icecrew•nl>
Cc: git@vger•kernel.org
Subject: Re: git gtk+/GNOME gui application: gitg
Date: Wed, 04 Feb 2009 15:29:15 +0100	[thread overview]
Message-ID: <4989A63B.4030103@drmicha.warpmail.net> (raw)
In-Reply-To: <1233432317.26364.5.camel@wren>

Jesse van den Kieboom venit, vidit, dixit 31.01.2009 21:05:
> Hi,
> 
> I have been developing a gui application for git for gtk+/GNOME based on
> GitX (which in turn is based on gitk). I feel that it's reaching the
> point where it might potentially be useful for other people to use. It
> currently features:
> 
> - Loading large repositories very fast
> - Show/browse repository history
> - Show highlighted revision diff
> - Browse file tree of a revision and export by drag and drop
> - Search in the revision history on subject, author or hash
> - Switch between history view of branches easily
> - Commit view providing per hunk stage/unstage and commit
> 
> The project is currently hosted on github:
> http://github.com/jessevdk/gitg
> 
> clone: git://github.com/jessevdk/gitg.git
> 
> Please let me know what you think,

OK, played with it, looks nice. Some feedback:

Bug:?
After unstaged a staged file it does not reappear under "unstaged". It
appears nowhere.

Build:
gitg can't run from the build dir, it needs to be installed.
Reconfiguring with different --prefix does not rebuild (one needs to
make clean manually).

Features:
Displaying the subject after the parent shas etc would be nice.
Maybe forward/back buttons for taking you forward/back in your *browsing
history*? Say, you click on a parent, and then you want to get back.
Can one stage hunks somehow?

Cheers,
Michael

  parent reply	other threads:[~2009-02-04 14:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31 20:05 git gtk+/GNOME gui application: gitg Jesse van den Kieboom
2009-02-03 13:08 ` SZEDER Gábor
2009-02-03 13:08   ` [PATCH 1/3] Fix "multi-character character constant" compile warning SZEDER Gábor
2009-02-03 13:08     ` [PATCH 2/3] Refactor loading xml UI files SZEDER Gábor
2009-02-03 13:08       ` [PATCH 3/3] Try load UI xml files from the current working directory SZEDER Gábor
2009-02-14 21:37       ` [PATCH 2/3] Refactor loading xml UI files Jesse van den Kieboom
2009-02-04 11:50     ` [PATCH 1/3] Fix "multi-character character constant" compile warning Jesse van den Kieboom
2009-02-03 16:58 ` git gtk+/GNOME gui application: gitg Michael J Gruber
2009-02-03 19:43   ` Stefan Karpinski
2009-02-04 11:50     ` Jesse van den Kieboom
2009-02-04  3:38   ` Miles Bader
2009-02-03 17:00 ` Jakub Narebski
     [not found]   ` <1233748909.7594.14.camel@wren>
2009-02-04 12:33     ` Jakub Narebski
2009-02-04  7:39 ` Felipe Contreras
2009-02-04 11:48   ` Jesse van den Kieboom
2009-02-04 12:46     ` Michael J Gruber
2009-02-04 14:12       ` Felipe Contreras
2009-02-04 14:18         ` Jesse van den Kieboom
2009-02-04 15:00           ` Felipe Contreras
2009-02-04 14:29 ` Michael J Gruber [this message]
2009-02-04 14:33   ` Jesse van den Kieboom
2009-02-04 14:40     ` Michael J Gruber
2009-02-04 14:46       ` Jesse van den Kieboom
2009-02-05  5:46 ` Miles Bader
2009-02-05 20:06   ` Jesse van den Kieboom
2009-02-06  9:49     ` Miles Bader

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=4989A63B.4030103@drmicha.warpmail.net \
    --to=git@drmicha$(echo .)warpmail.net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jesse@icecrew$(echo .)nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox