openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Kovacs <Pe...@Apache.org>
Subject Re: [resolution] svn migration plan
Date Sat, 03 Aug 2019 05:47:09 GMT
Hello all,

I have pushed Infra a bit. We are now migrating.

So migration will be finished soon.


I suggest we use the short hash.


I will try to change the Code link.

What else do we need to do?


Sorry if this moves now a bit uncoordinated, but I want to get this done.


On 29.07.19 20:39, Peter Kovacs wrote:

> On 29.07.19 17:18, Matthias Seidel wrote:
>> Hi Peter,
>>
>> Am 29.07.19 um 00:39 schrieb Peter Kovacs:
>>> A different suggestion we use the git commit count. The command is:
>>>
>>> |git rev-list --all --count It will deliver something that looks similar
>>> to the svn number we already use. All the Best Peter |
>> How would such a simple count point to a specific commit/revision?
>>
> I checked this,. In theory it should but there are a lots of option how
> to count in git.
>
> Which makes this not so optimal as on first glance. But it seems a lot
> of people use it to stick to a revision number.
>
> So there seems to be only 2 true options for referencing the commit:
>
> 1) We use the short hash.
>
> 2) We tag releases automatically at checkin.
>
>
> Tbh I would rather use the v
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Mime
View raw message