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


Hi all,

I commited an initial proposal of an awk script that creates a shell
script to create a annotated commit on master. It is here:

 
http://cgit.freedesktop.org/libreoffice/build/tree/patches/dev300/extractapplyinfo.awk?id=4345b801c95cbff319bd69be844a98488bef3bfd

To use it you would (usually in batches of multiple patches):
 - cd build/patches/dev300
 - awk -f extractapplyinfo.awk -v PATCHNAME=foo.diff > migrate-foo.sh
 - fixup migrate-foo.sh
 - run bash migrate-foo.sh with an set environment
   (having $SOLARSRC set is enough)

Open points:
 - it currently uses --no-verify, because of whitespace in the git logs
   included in the commit message
 - we should fixup the authors in the apply file to all conform to the
   A U Thor <author@example.com> format beofre migration
 - the script (unlike the one I had before and accidentally deleted
   before commiting) ignores "SectionIssue" syntax. We should just add
   those issue numbers behind the patch on the line.
 - Before we start migrating, we should decide if the generated commit
   message is not totally disgusting to anyone involved. As such
   discussions generally can take longer that the usual editor
   flamewar, I would like to set a deadline on this right here right
   now: We should use whatever is current state this Friday at noon UTC.

Comments welcome!

Best Regards,

Bjoern

-- 
https://launchpad.net/~bjoern-michaelsen

Attachment: signature.asc
Description: PGP signature


Context


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.