Hi,
On Tue, Apr 9, 2013 at 10:55 AM, Jeremy Rosen wrote:
> 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 cau
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
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
Opps, somehow I forgot to actually attach it.
It's now attached
graph_git.pl
Description: Binary data
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 he
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 gr
6 matches
Mail list logo