From: Michael J Gruber <git@drmicha•warpmail.net>
To: Jesse van den Kieboom <jesse@icecrew•nl>
Cc: Felipe Contreras <felipe.contreras@gmail•com>, git@vger•kernel.org
Subject: Re: git gtk+/GNOME gui application: gitg
Date: Wed, 04 Feb 2009 13:46:34 +0100 [thread overview]
Message-ID: <49898E2A.7070005@drmicha.warpmail.net> (raw)
In-Reply-To: <1233748114.7594.0.camel@wren>
Jesse van den Kieboom venit, vidit, dixit 04.02.2009 12:48:
> Op woensdag 04-02-2009 om 09:39 uur [tijdzone +0200], schreef Felipe
> Contreras:
>> On Sat, Jan 31, 2009 at 10:05 PM, Jesse van den Kieboom
>> <jesse@icecrew•nl> wrote:
>>> 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,
>> And the obligatory screenshots?
>
> The screenshots are on the website
Grin ;) At least I'm not the only one who didn't how to navigate the
github page...
In fact, reading the top line there in the first place would have made
me hopeful that this is a unifying rather than splitting project. So, my
best wishes (I'll try and compile)!
Cheers,
Michael
next prev parent reply other threads:[~2009-02-04 12:48 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 [this message]
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
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=49898E2A.7070005@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=felipe.contreras@gmail$(echo .)com \
--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