home :: software :: finding-forks

Tue, 21 Aug 2012

Finding forks.

github has become the place where a lot of code is made available.

It turns out that not everyone has the time or inclination to answer queries / questions or apply pull requests.

So, whenever I am investigating using something I've found, I always look to see what the forks are; if there are common issues, etc.

In the past, I've done this by hand, for small repositories it isn't too time consuming. Today, though, I sat down and wrote find-forks.py which will do this automatically.

Now, I find a project, clone it, run ./find-forks.py and settle down with gitk to examine the history and various other forks.

This works well for me, feel free to use or improve as you like. I hereby place this in the Public Domain.

[ / software] Trackbacks (0) Comments (0) permanent link permanent link

Trackbacks

Trackbacks are closed for this story.

Comments

Submit a comment

Comments are closed for this story.

About

ॐ (aum) - what was, what is and what will be, wildfire's musings

Anand Kumria
wildfire@progsoc.org

Calendar

Topics

beauty - 1
blogging - 4
books - 1
comms - 1
debian - 7
django - 4
ebay - 1
edinburgh - 8
finance - 1
freedom - 2
general - 4
hardware - 3
dell - 2
disks - 1
health - 3
helsinki - 1
learning - 1
london - 1
review - 1
movies - 1
salsa - 1
security - 2
software - 22
blosxom - 2
gnome - 1
moblog - 1
ubuntu - 1
vcs - 2
zeroconf - 1
sydney - 8
isp - 3
thisisbroken - 2
travel - 1
work - 2
awayphone - 1
general - 1

Subscribe

Subscribe to a syndicated feed of my weblog, brought to you by the wonders of Atom.

Music

Blosxom

Rendered in only 0.9199 seconds.

ॐ (aum) - what was, what is and what will be