From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756902AbbCMUUQ (ORCPT <rfc822;w@1wt.eu>);
	Fri, 13 Mar 2015 16:20:16 -0400
Received: from cpsmtpb-ews05.kpnxchange.com ([213.75.39.8]:58519 "EHLO
	cpsmtpb-ews05.kpnxchange.com" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1752170AbbCMUUL (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 13 Mar 2015 16:20:11 -0400
Message-ID: <1426278008.7778.27.camel@x220>
Subject: Re: [PATCH] checkkconfigsymbols.py: make it Git aware
From: Paul Bolle <pebolle@tiscali.nl>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
        hengelein Stefan <stefan.hengelein@fau.de>,
        linux-kernel@vger.kernel.org, Andreas Ruprecht <rupran@einserver.de>
Date: Fri, 13 Mar 2015 21:20:08 +0100
In-Reply-To: <CAD3Xx4+N=J5Bf6HX2Oe+=vSzWyKrRRpZqtVLjub-H1cCf-9zKQ@mail.gmail.com>
References: <1426072565-22296-1-git-send-email-valentinrothberg@gmail.com>
	 <1426075485.4244.112.camel@x220>
	 <CAD3Xx4LR8pUQnFp-h5BRG08Ujkj5hKzF2G9TJRD5-C+jaNsPTQ@mail.gmail.com>
	 <CAD3Xx4Kp8griLJrR3H7G2AU0_YZeV-xvrdnxV-dTr=YuDmop9w@mail.gmail.com>
	 <CAD3Xx4+N=J5Bf6HX2Oe+=vSzWyKrRRpZqtVLjub-H1cCf-9zKQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Mar 2015 20:20:09.0567 (UTC) FILETIME=[1A5B26F0:01D05DCB]
X-RcptDomain: vger.kernel.org
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 2015-03-11 at 16:04 +0100, Valentin Rothberg wrote:
> Paul, how long does your monster run?  Maybe I just call it wrong or
> mess up with caches.

Even longer, I presume. Because an update for just a new linux next
release can take over a minute on my fastest machine (a ThinkPad X220).

(Recall that my monster runs daily over just the blobs added to the tree
for the latest linux-next tag and stores an intermediate parse as a git
note to each of those new blobs. It then does a second parse of all the
git notes relevant for that tag and stores the final result as a git
note to that tag.

And I do all this to make the daily update run at a decent speed. A
downside of this approach is that the very first run, which has to
parse, say, 50.000 new blobs, takes ages.)

My suggestion won't do here. So let me just say that messing with the
state of peoples repository might make you the target of a flame or two.
Are you sure you want to go down that route?


Paul Bolle