Blair Zajac wrote:
> David Glasser wrote:
>> On 7/27/07, Blair Zajac <blair@orcaware.com> wrote:
>>> It also may be safer to always put the revision number into the new 1.5
>>> transaction ids (<rev>-<base36-sequence-number>), just in case
>>> there's something
>>> else that hasn't been considered, as the current code works fine when
>>> this is done.
>>
>> Independently of the actual issue you're raising, I definitely find it
>> to be helpful that fsfs txn ids have the revision number in them: it
>> makes the out of date error messages slightly easier to understand,
>> helps with svnadmin lstxns, etc.
>
> Thanks. I'll definitely keep them in there then.
BTW, I think the BDB transaction names do not include the revision number in the
transaction name. Should we make BDB use the same format <rev>-<base36-number>
as the new fsfs transaction names for consistency?
Also, I've decided to only support the new txn sequence number in repositories
created in 1.5 and left the old code in for repositories created by/for 1.4 or
earlier.
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 27 23:55:12 2007