current "fresh" release not tagged in git?
Christian Lohmaier
lohmaier at googlemail.com
Mon May 18 17:23:28 PDT 2015
Hi Richard, *,
On Mon, May 18, 2015 at 2:18 PM, Richard Cochran
<richardcochran at gmail.com> wrote:
> On Mon, May 18, 2015 at 01:50:42PM +0200, Richard Cochran wrote:
>> On Mon, May 18, 2015 at 12:21:24PM +0200, Rene Engelhard wrote:
>> > Forgot git fetch --tags?
>>
>> I did 'git remote update origin', and I thought that includes tags.
>
> Now I see. The tag 'libreoffice-4.4.3.2' is not the branch called
> 'libreoffice-4-4-3'. In fact, is isn't on any branch at all, AFAICT.
Yes, thats correct, like all the tags before it is on its separate
"mini-branch" that has the version change and the commit that labels
the tag. The mini-branches don't have a name, but are referenced using
the tag.
So tree looks like this:
----------------------------------------------------- libreoffice-4-4-3 branch
\---version bump to 4.4.3.1 \----version bump to 4.4.3.2
\-- "this is tag 4.4.3 rc1" [tagged] \--- "this is tag 4.4.3 rc2" [tagged]
ciao
Christian
More information about the LibreOffice
mailing list