Hi Andrea,

Am 25.10.18 um 23:42 schrieb Andrea Pescetti:
> On 23/10/2018 Matthias Seidel wrote:
>> Am 23.10.18 um 13:06 schrieb Jim Jagielski:
>>> r1844555 was the SVN version of HEAD at the time of the email.
>> Yes, and it increases by the time of writing...
>> So it gives no information about what revision the RC should be build
>> upon?
>
> This has always been an issue to the structure of our SVN repository,
> but fortunately it is only cosmetic.
>
> All the ASF projects use the same SVN repository, and the revision
> number increases (obviously) any time someone commits to any part of
> the repository. So a commit to another project will increase the
> overall revision number while the OpenOffice code remains the same.
>
> This means there is always a range of SVN HEAD revisions that
> correspond to the same OpenOffice code. Only running "svn log" in the
> OpenOffice checkout will tell you the last "real" OpenOffice revision.

"svn info" gives you both revisions. At least that's what I am using.

---
$ svn info
Pfad: .
Wurzelpfad der Arbeitskopie: /cygdrive/c/Source/aoo-416
URL: https://svn.apache.org/repos/asf/openoffice/branches/AOO416
Relative URL: ^/openoffice/branches/AOO416
Basis des Projektarchivs: https://svn.apache.org/repos/asf
UUID des Projektarchivs: 13f79535-47bb-0310-9956-ffa450edef68
Revision: 1844630
Knotentyp: Verzeichnis
Plan: normal
Letzter Autor: mseidel
Letzte geänderte Rev: 1844436
Letztes Änderungsdatum: 2018-10-20 23:55:27 +0200 (Sa, 20. Okt 2018)
---

>
> I think we used to have a double numbering, like "revision 1844555
> corresponding to openoffice revision 1844436"... but this only made it
> more confusing!

We have this double numbering in some builds from our buildbots and it
still confuses people... ;-)

Regards,

   Matthias

>
> Regards,
>   Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to