Nomenclature

[John A Meinel]

Gustavo Niemeyer wrote:
>>>Same case.. either branch.get_revision_history() and
>>>branch.get_revision(), or branch.revision_history() and
>>>branch.revision().
>>
>>Actually, there is a very significant difference here.
>>branch.revision_history() is give me the revision history of this 
>>branch. (A property of this branch).
>>branch.revision() would say to me tell me what the revision of this 
>>branch is. But really branch.get_revision() is giving you some 
>>information about a particular revision.
>>
>>The issue is that some functions are attributes of branch, and some are 
>>coming from the data that branch stores.
> 
> 
> So you mean that branch.common_ancestor() will give you
> the common ancestor this branch, and that branch.get_parent()
> will give you the parent of a particular revision?

I thought it was:

common_ancestor(b1, b2)

But maybe there is a newer function.

branch.get_parent() is because you need to have a branch.set_parent().

> 
> ;-)
> 
> 
>>>>>* branch.get_rev_id() vs. branch.revision_id_to_revno() vs. *.id2*()
>>>>
>>>>get_rev_id translates the above revno into a revision_id. 
>>>>revision_id_to_revno is the opposite translation.
>>>
>>>
>>>Same case. If they are exactly the opposite of each other, why one
>>>is named get_rev_id() and the other revision_id_to_revno()? :-)
>>
>>I'm guessing because one is used far more than the other. :)
> 
> 
> Ouch :-)
> 

But actually, if you have a great way of unifying everything, I'll be 
happy to use it.
I'm just trying to discuss what nomenclature should be.
That and the people who really matter are asleep right now in Australia.

John
=:->

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050930/36ef38ae/attachment.pgp