Hi all, Any progress?
Git is active since Saturday. SVN is now read only (for trunk, branches and tags). New Builds do not contain any revision information. We have documentation that must be updated asap, e.g.: https://openoffice.apache.org/source.html Who wants to write a blog post or post *any* kind of information for the public? It remains a mystery for me why this hasn't been discussed and planned prior to the switch... Regards, Matthias Am 03.08.19 um 14:09 schrieb Matthias Seidel: > Hi Mechtilde, > > Am 03.08.19 um 13:56 schrieb Mechtilde: >> Hello, >> >> I looked into >> >> main/solenv/bin/modules/SvnRevision.pm:39 >> >> There we have to change the condition for the "Revision ID" >> >> Instead of the condition for the git-svn-id we should take the hash >> which followed to the word "commit" in the first line. >> >> Here is an ouput with git show HEAD from last commit in AOO42X >> >> 1. commit 7b7ead25a5e14edc410cfd3b24d145ab38514b11 (HEAD -> AOO42X, >> origin/AOO42X) >> 2. Author: Matthias Seidel <[email protected]> >> 3. Date: Fri Aug 2 18:45:56 2019 +0000 >> 4. >> 5. Merged r1864263 from trunk >> 6. >> 7. Cleaned up whitespace, reordered Increase/Decrease Indent in sidebar >> 8. >> 9. git-svn-id: >> https://svn.apache.org/repos/asf/openoffice/branches/AOO42X@1864280 >> 13f79535-47bb-0310-9956-ffa450edef68 > Only to clarify: > > This commit still contains the git-svn-id. > Newer commits will not have it, so the revision in our About dialog will > stay blank. > (I am just doing a build to clarify) > > Regards, > > Matthias > >> I added the line numbers for better reading. >> >> Can someone wrote the right Regular Expression in Perl. >> >> Kind regards >>
smime.p7s
Description: S/MIME Cryptographic Signature
