Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

Cor Nouws píše v Čt 10. 05. 2012 v 17:32 +0200:
Hi Petr,

Petr Mladek wrote (10-05-12 17:11)

Wonderful. Could you please cut&paste them? I wonder how they look like.

thanks for your interest!
Attached an ods with the rough data I have now.

The list of selected changes look reasonable to me. I just suggest two

   + add name of the author
   + slightly reword each commit summary to get a consistent look and

I mean to get something like the GNOME digest, see

Thinking about a strategy to get that in WordPress quickly (without 
difficult mouse editing of links... Someone a hint?) :-\
(will post part of it, will keep part for next blog)

When I announce builds for openSUSE, I cut&paste the previous
announcement. Most of the links are the same.

If you want to add links to bugzilla, I could create a simple script for
you. It will replace fdo#xxxxx with the needed tags for WordPress. I
guess that it uses html tags. Does it?

BTW: How did you collect them? The following ways come to my mind:

    + git changelog:

Yup, just this. I see it once or sometimes more each day. And picking 
out interesting stuff goes fast after some practising ;-)

Cool. Thanks a lot for working on it.

Best Regards,

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.