At the risk of being wrong, because I didn't check myself ... what SVN reports is that you checked the latest version he has (because you didn't specify the -r switch) ... globally. Probably if you do an:

svn log

on the sources you check'd out, you'll see the "true" revision ... well, really more like the last commit done on this branch ...

Cesc

On 3/13/07, Klaus Darilion klaus.mailinglists@pernau.at wrote:

Hi!

I've checked out branch 1.2 using: svn co https://openser.svn.sourceforge.net/svnroot/openser/branches/1.2/ openser ... ... A openser/radius.h A openser/qvalue.c U openser Checked out revision 1836.

Why has it checked out revision 1836? commit 1836 was Juha's LCR AVP changes which were applied to trunk.

Taking a look at Makefile.defs I see that I've checked out 1.2, but why does svnversion report 1836?

Maybe someone can shortly explain this.

thanks klaus

-- Klaus Darilion nic.at

---

Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users

Klaus Darilion wrote:

Hi!

I've checked out branch 1.2 using: svn co https://openser.svn.sourceforge.net/svnroot/openser/branches/1.2/ openser ... ... A openser/radius.h A openser/qvalue.c U openser Checked out revision 1836.

Why has it checked out revision 1836? commit 1836 was Juha's LCR AVP changes which were applied to trunk.

Taking a look at Makefile.defs I see that I've checked out 1.2, but why does svnversion report 1836?

With svn you have one revision number per repository and not like with cvs per project. So each time someone commits something to the openser svn repository the revision number will change. Since the openser svn repository (http://openser.svn.sourceforge.net/viewvc/openser/) includes trunk, tags, branches, what you've observed looks ok to me.

Christian

Maybe someone can shortly explain this.

thanks klaus