From: Pratyush Yadav <me@yadavpratyush.com>
To: Insane Sharpness <insane.sharpness@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: New Git Visualiser Tool - GitVine
Date: Fri, 20 Dec 2019 01:23:03 +0530 [thread overview]
Message-ID: <20191219195303.ckeuucm5c7n56eew@yadavpratyush.com> (raw)
In-Reply-To: <CAMNO-Ba0-Me67qEEfHoJyBoWg0X_x7=qmmZ1D8ZK9S_0Tk=J5Q@mail.gmail.com>
Hi,
On 19/12/19 10:53AM, Insane Sharpness wrote:
> Hey All,
>
> I made an application recently to better visualise git commits on a
> per file basis.
> And added this to the git kernel wiki here
> https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools#GitVine
>
> Does not try to compete with more feature rich & powerful clients like
> Gitk, Kraken etc..
> Just tries to be simpler.
>
> Free Standalone & runs on Windows, Linux & macOS
> Just needs git in your path. (Developed using Python, Qt & packaged
> with PyInstaller)
> Project Page Here: https://insanesharpness.gitlab.io/GitVine/
>
> Its still a rough cut and loads of room to improve + add more features.
> Please try, would love to hear what you all think.
I have only used it for a few minutes, but one thing I immediately
noticed is that the startup time is _really_ slow. On the git-gui repo
[0] with only about 1200 commits, it takes around 10-15 seconds to load.
On the git.git repo [1] with around 57,000 commits, it takes nearly two
minutes to load. In comparison, gitk it almost instant. These two repos
are relatively small in size, and examples of bigger ones would be
Linux, Chromium, etc where I expect startup times to be even slower.
I'm running it on Linux on Git v2.24.1. Speeding up the startup time
would be really nice.
The log for git-gui is missing some merge commits like d32e065 and
2763530 but then it shows some other merges like 69fdb92. I'm not sure
why this inconsistency happens. This also leads to the tool showing
39acfa3 as the HEAD (as of writing this it is also the 'master') when in
reality the HEAD is at d32e065.
Also, when I double click a commit in the list at the right side, a
popup opens with the commit information like hash, author, commit
message, etc. But, I notice that the "Signed-off-by" trailers are
missing the email addresses. The popup when hovering over a node in the
graph shows them correctly though. So, for example the trailers of
39acfa3 are:
Signed-off-by: Kazuhiro Kato <kato-k@ksysllc.co.jp>
Signed-off-by: Pratyush Yadav <me@yadavpratyush.com>
But they show up as:
Signed-off-by: Kazuhiro Kato
Signed-off-by: Pratyush Yadav
All this said, I like the simple and clean UI. Looking forward to how
the tool grows :)
[0] https://github.com/prati0100/git-gui
[1] https://github.com/git/git
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2019-12-19 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 10:53 New Git Visualiser Tool - GitVine Insane Sharpness
2019-12-19 19:53 ` Pratyush Yadav [this message]
2019-12-19 20:16 ` Insane Sharpness
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=20191219195303.ckeuucm5c7n56eew@yadavpratyush.com \
--to=me@yadavpratyush.com \
--cc=git@vger.kernel.org \
--cc=insane.sharpness@gmail.com \
/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).