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: Tue, 9 Apr 2013 10:55:06 +0200 (CEST) [thread overview]
Message-ID: <1344434918.1379702.1365497705958.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <CAHQ6N+rPfYmNRjjU0EDx3B1O_K+c6zm9v=BT_bMEXZ1yQFXGhw@mail.gmail.com>
looking a little bit more into this, I was very suprised....
there seems to be little/no tools in the git ecosystem that studies the dependencies between commits based on the file they modified and/or the conflict they would cause.
Is there any pre-existing tool to do that ? It can be done with git-log --name-only(the graph_git.pl is just a graphing layer above that command) but i'm suprised that I couldn't find anything else
And that was at the file level, is there any tool to help find what commits can be reordered without causing conflicts ? I am not sure if there is an easy way to extract potential conflict information from git...
Regards
Jérémy Rosen
fight key loggers : write some perl using vim
----- Mail original -----
> Hi Jeremy,
>
> It would be great if you could send your email again to the list,
> so
> that other people can see that there is interest in my script :)
> Makes it easier for me to get it included.
>
> > * 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
>
> Yes, tooltips are a real pain. I don't know how to do that.
>
> > * I would love to have tooltips on the arrows too. when trying to
> > follow what arrow is what file it makes things really handi
>
> Actually they do have tooltips - it's just that the arrows are really
> thin so you have to be very accurate with your mouse pointing!
>
> > 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
>
> Try just specifying the files:
>
> $ graph_git.pl -10 filename1 filename2
>
> I haven't tested, but it should work
>
> > is there a public repo for this script so I can point other people
> > to it ?
>
> No - any suggestions as to where to put it are welcome :)
>
> John
>
next parent reply other threads:[~2013-04-09 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHQ6N+rPfYmNRjjU0EDx3B1O_K+c6zm9v=BT_bMEXZ1yQFXGhw@mail.gmail.com>
2013-04-09 8:55 ` Jeremy Rosen [this message]
2013-04-09 14:02 ` RFC: Very useful script to SVG graph the git commits from a file orientated view Christian Couder
2013-04-04 12:36 John Tapsell
2013-04-04 12:46 ` Jeremy Rosen
2013-04-04 12:50 ` John Tapsell
2013-04-08 10:49 ` Jeremy Rosen
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=1344434918.1379702.1365497705958.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).