From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: John Tapsell <johnflux@gmail.com>, Git List <git@vger.kernel.org>
Subject: Re: RFC: Very useful script to SVG graph the git commits from a file orientated view
Date: Mon, 8 Apr 2013 12:49:55 +0200 (CEST) [thread overview]
Message-ID: <1230283897.1259692.1365418195898.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <CAHQ6N+r7RpV3n+Mb3GEyJim7-bwML_OUmveLZjWcRWp_HF-rNQ@mail.gmail.com>
so, I started using it this WE for my big rebase
I had aproximately 130 non-merge commits in my branch, a feature branch in which I had regularly merged master, but I needed to rebase everything and then reorganise most commits to make the whole thing reviewable
* merge bug-fix with the commit that introduced the bug
* change sloppy commit messages
* separate sloppy commit into multiple commits
I did my initial rebase and I am now doing repetitive "git rebase -i" to get everything going
your script is very usefull to me because it allows me to easily see the overall layout of things and figure what commit are "suspect" (touching files from different areas that have no reasons to be touched at the same time)
it also allows me to easily find commits that are highly connected to other ones and are the most likely to be problematic when reordering commits. Overall that script is awesome.
couple of ideas to refine things
* The tooltips are very handy, but it would be nice if the tooltip would activate on the whole commit ellipsis, not just the text inside the ellipsis
* I would love to have tooltips on the arrows too. when trying to follow what arrow is what file it makes things really handi
It would be nice if there were a way to filter only some files in the output... there probably is with the git-log like syntax but i'm not a master of that... hints would be welcome
is there a public repo for this script so I can point other people to it ?
Cordialement
Jérémy Rosen
fight key loggers : write some perl using vim
----- Mail original -----
> Opps, somehow I forgot to actually attach it.
>
> It's now attached
>
next prev parent reply other threads:[~2013-04-08 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 12:36 RFC: Very useful script to SVG graph the git commits from a file orientated view John Tapsell
2013-04-04 12:46 ` Jeremy Rosen
2013-04-04 12:50 ` John Tapsell
2013-04-08 10:49 ` Jeremy Rosen [this message]
[not found] <CAHQ6N+rPfYmNRjjU0EDx3B1O_K+c6zm9v=BT_bMEXZ1yQFXGhw@mail.gmail.com>
2013-04-09 8:55 ` Jeremy Rosen
2013-04-09 14:02 ` Christian Couder
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=1230283897.1259692.1365418195898.JavaMail.root@openwide.fr \
--to=jeremy.rosen@openwide.fr \
--cc=git@vger.kernel.org \
--cc=johnflux@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.
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).