From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: John Tapsell <johnflux@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: RFC: Very useful script to SVG graph the git commits from a file orientated view
Date: Thu, 4 Apr 2013 14:46:57 +0200 (CEST) [thread overview]
Message-ID: <759444160.1179815.1365079617652.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <CAHQ6N+qLbrBKWhq8OGKco+JxiiLVOQvW09j3rLeZw265POZuMw@mail.gmail.com>
very usefull indeed, where can I find it ? I have a big rebase/merge/reorganise work that is comming soon and that is going to be tremendously usefull...
Cordialement
Jérémy Rosen
fight key loggers : write some perl using vim
----- Mail original -----
> Hi,
> I made this script to help me see the logical connections between
> commits. It produces a .svg graph showing the commits that affected
> a
> file.
>
> For example, say you have the commits:
>
> commit1 - modify hello.c
> commit2 - modify goodbye.c
> commit3 - modify hello.c and goodbye.c
>
> It will draw a graph showing the first two commits as siblings, and
> commit3 as a child of commit1 and commit2.
>
> I have found this very useful when squashing and rebasing development
> branches that have got a lot of "fix typo" and "fix" type commit
> messages. From the graph you can quickly see which commit they were
> fixing (the parent, in the graph).
>
> Here is an example output, running it on kwin for the last 100
> commits:
>
> $ graph_git.pl --nofiles -100
>
> http://imagebin.org/252754
>
> And again with files for the last 10 commits:
>
> $ graph_git.pl -10
>
> http://imagebin.org/252756
>
> (Note that it has tooltips)
>
> JohnFlux
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-04-04 12:47 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 [this message]
2013-04-04 12:50 ` John Tapsell
2013-04-08 10:49 ` Jeremy Rosen
[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=759444160.1179815.1365079617652.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).