Steven Velez <svelez@alventive.com> writes:
> The global repository revision has been something that I have never really
> been comfortable with since I started following subversion development.
> Some of it is because it's not what I'm used to but, more of it is it seems
> that it good gets too big fast. I mean, how is that revision number stored?
> Even if it's a unsigned 32 bit integer, I would not feel comfortable saying,
> "Well, you can make 4.3 billion separate commits to the repository and then
> you're hosed." It would be a bigger problem in bigger code-bases with more
> developers...... however, I'm sure this has already been considered and I'm
> just showing my ignorance but I would feel better to know the detail here in
> particular.
Given that a time_t is also a signed 32-bit integer and 68 years exist
between 1970 and 2038, this means you can commit every second for the
next 68 years and not run out of revisions.
But beyond that: our code uses a custom 'svn_revnum_t' type, which we
can define to be whatever we want in the future. We're thinking,
actually, of switching all our revision "numbers" to arbitrary hex
strings soon. Just to stop people from thinking that it means
anything important about their project. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 3 18:54:21 2002