On Sun, 5 Sep 2010 at 14:08, Marcus Rueckert wrote:
you want to read it again. it is a script that is generating stats and overview pages from those lines, not his editor.
such a script should be running on the server side where opening a file and reading a few line is cheap. OTOH, depending on the individual packager's habits, metadata that is put into the patch file can easily get lost. So my conclusion is, that if we really fail to get the build service itself to track it for us (including branches and submits), the best place to track description *and* history of a patch is the package change log (either the .changes file or the %changelog section of the spec file). cu Reinhard -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org