Comments on: Announcing git-deps: commit dependency analysis / visualization tool https://blog.adamspiers.org/2015/01/19/git-deps/ because there's always something more interesting than what you should be doing Sat, 24 Jan 2015 01:14:45 +0000 hourly 1 https://wordpress.org/?v=7.0.2 By: OpenStack Community Weekly Newsletter (Jan 16 – 23) | The OpenStack Blog https://blog.adamspiers.org/2015/01/19/git-deps/#comment-1653040 Sat, 24 Jan 2015 01:14:45 +0000 http://blog.adamspiers.org/?p=1452#comment-1653040 […] Announcing git-deps: commit dependency analysis / visualization tool […]

]]> By: Adam https://blog.adamspiers.org/2015/01/19/git-deps/#comment-1650342 Mon, 19 Jan 2015 14:17:21 +0000 http://blog.adamspiers.org/?p=1452#comment-1650342 In reply to Matthijs Kooijman.

Hi Matthijs! It’s funny – actually I just discovered `patchdeps` a few hours before you wrote this 🙂 Before I first wrote git-deps in late 2013 I googled around for any existing tools but didn’t find yours for some reason :-/ Otherwise I would have tried to build on yours instead of reinventing the wheel – sorry about that. But yes, it is a slightly different approach, although yours has the advantage of working with other SCMs I guess.

]]> By: Matthijs Kooijman https://blog.adamspiers.org/2015/01/19/git-deps/#comment-1650330 Mon, 19 Jan 2015 13:48:10 +0000 http://blog.adamspiers.org/?p=1452#comment-1650330 Nice tool! I previously wrote `patchdeps`, a similar tool which handles both patches and git commits by manually analyzing the diff output. Your approach of just parsing git blame output looks great to me, the code is a lot simpler.

At some point I got stuck at not being able to properly find dependencies without looking at the entire history when some more complex merges were involved. It seems your code just lets git sort this stuff out through blame 🙂

I’ll keep this tool in mind the next time I have a bunch of patches to sort out 🙂

]]>