From: Jesse van den Kieboom <jesse@icecrew.nl>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: git gtk+/GNOME gui application: gitg
Date: Wed, 04 Feb 2009 15:46:08 +0100 [thread overview]
Message-ID: <1233758768.7594.27.camel@wren> (raw)
In-Reply-To: <4989A8E7.6080109@drmicha.warpmail.net>
Op woensdag 04-02-2009 om 15:40 uur [tijdzone +0100], schreef Michael J
Gruber:
> Jesse van den Kieboom venit, vidit, dixit 04.02.2009 15:33:
> > Op woensdag 04-02-2009 om 15:29 uur [tijdzone +0100], schreef Michael J
> > Gruber:
> >> 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.
> >
> > Hmm this _should_ happen, if it doesn't it's certainly a bug.
>
> I just compared with staging/reverting the single hunk I had in there,
> that works perfectly. The bug occurs only when unstaging from the list
> of staged files.
>
> >> 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).
> >
> > This is true, I got a patch to fix this, but I'm not sure it should go
> > in (e.g. read data files from current working directory). It's not
> > common to be able to run C/gtk+ apps from the build directory, you
> > should install them in a local prefix.
>
> Sure, but just to try it out? Imagine me poor soul, going through all
> these GUIs and cloning, running
> autogen.sh/qmake-qt4/configure/make/setup.py depending on the tk, and
> finding I have to install in order to try it out (not to mention
> dependencies)? ;)
Yeah I know, it's a hassle. But fixing this would involve quite some
hacks in the code (it's not just the ui xml files, also icons and other
installed data) to find this data. Unfortunately, autotools is not
really friendly in this way. It might be possible to build binaries
which have local resources (like OS X bundles) so it can be tried out
without installing, but I'm not sure it's worth the effort.
> >> Can one stage hunks somehow?
> >
> > Yes, you can click on the hunk header @@...@@ when viewing the diff in
> > the commit view. You can also rightclick on this header and revert a
> > hunk (or stage/unstage it from the context menu).
>
> Uh, thanks, works like a charm. I had tried selecting and right-clicking
> the hunk itself...
>
> Cheers,
> Michael
>
--
Jesse van den Kieboom
Personal: http://www.icecrew.nl
Professional: http://www.novowork.com
next prev parent reply other threads:[~2009-02-04 14: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
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 [this message]
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=1233758768.7594.27.camel@wren \
--to=jesse@icecrew.nl \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).