From 7d2ad2fac50388643bd2904ae0515b65bae20074 Mon Sep 17 00:00:00 2001 From: Jonathan Corbet Date: Mon, 30 Dec 2013 16:02:21 -0700 Subject: Respond properly to a missing commit Looping forever until the disk fills is somewhat antisocial behavior; they taught me that somewhere in grad school, I'm sure... --- firstlast | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/firstlast b/firstlast index d07218c..6c8fc8a 100755 --- a/firstlast +++ b/firstlast @@ -79,8 +79,15 @@ def PrintFirstEmpls(): empls = FirstEmpls.keys() empls.sort(cmpempls) print '\nEmployers:' - for e in empls[:20]: + for e in empls[:30]: print '%5d: %s' % (FirstEmpls[e], e) + # + # We "know" that unknown/none are always the top two... + # + companies = 0 + for e in empls[2:]: + companies += FirstEmpls[e] + print 'Companies: %d' % (companies) # # Version comparison stuff. Kernel-specific, obviously. @@ -133,6 +140,7 @@ while patch: v = VDB[patch.commit] except KeyError: print 'Funky commit', patch.commit + patch = gitlog.grabpatch(sys.stdin) continue # # The first patch we see is the last they committed, since git -- cgit v1.2.3