[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[dev] GIT Tags - Re: [ANNOUNCEMENT] 'ODF Toolkit 1.0.0 BETA' & 'ODF Toolkit 0.9.0 Release Candidate'

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


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

Am Mo., 7. Okt. 2019 um 12:44 Uhr schrieb Michael Stahl <mst@libreoffice.org

> ...
> i don't see a tag for the release candidate in git - could you please
> tag the commit so i can be confident that i'm building the right commit
> for testing?

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

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.