Vincent Lefevre wrote:
> On Tue, Jul 22, 2003 at 16:17:29 +0100, Philip Martin wrote:
>
>>If it is not clear what the revision represents then it is not
>>useful. I think a. would be OK if it was clear that this is what the
>>revision represents
>>
>> Version 0.26.0 (released 24 July 2003, branched from revision XXXX)
>>
>>
>>>I seem to recall someone (Philip?) mentioning that Michael Price used
>>>to 'guess'. I'm just not clear on what he based his guess on :)
>>
>>As I understand it, Michael made the branch, committed any changes
>>required, and then as the final commit on the branch updated XXXX to
>>the revision of that final commit. This required him to 'guess' the
>>revision number of the final commit (as HEAD plus one), and it worked
>>provided HEAD didn't change while he was preparing or making the
>>commit.
>
>
> Can't the above line be automatically generated so that a 'guess'
> is no longer necessary?
I've searched for it, but can't find it. The answer is: No not at this
moment. OTOH, i've seen it mentioned that something like this is
in the making. I think i've seen it both on the mailing list as
well as in IssueZilla. It was some kind of 'one-time' keyword that
got subsituted to flat text (e.g. the next revision number) and then
lost the 'status' of being a keyword, just plain text.
Hope that this helps a bit,
Jilles Oldenbeuving
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 23 17:40:12 2003