Date: prev next · Thread: first prev next last


On 08.10.19 12:58, Svante Schubert wrote:
Hi Michael,

Thanks for asking, I was not aware that the GIT tags are not being pushed, I did push the local tags now:

svante@devel:~/dev/tdf-odftoolkit$ *git push --follow-tags*
Username for 'https://github.com': svanteschubert
Password for 'https://svanteschubert@github.com':
Enumerating objects: 2, done.
Counting objects: 100% (2/2), done.
Delta compression using up to 4 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (2/2), 369 bytes | 369.00 KiB/s, done.
Total 2 (delta 0), reused 0 (delta 0)
To https://github.com/tdf/odftoolkit.git
  * [new tag]           odftoolkit-0.9.0-RC1 -> odftoolkit-0.9.0-RC1
  * [new tag]           odftoolkit-1.0.0-BETA1 -> odftoolkit-1.0.0-BETA1

thanks, maybe i'll have a look later today, but this XHTML stuff is such an annoyance, now people complain that the browser with 90 % market share doesn't support MathML properly...

Cheers,
Svante

PS: Is there an easy common way in GIT to pull & push the changes in all branches?

try: git push --all

but as usual, best to first check with --dry-run what you're going to push...

--
To unsubscribe e-mail to: dev+unsubscribe@odftoolkit.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.odftoolkit.org/dev/
Privacy Policy: https://www.documentfoundation.org/privacy

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.