Aaron> It's a feature. It keeps the model simple. It allows the
Aaron> aliases to vary independently. It allows the original command be
Aaron> given an alias, while an alias is created for the original name.
OK. I'm trying to adjust to the model...
Aaron> I don't think so. User aliases and built-in aliases are
Aaron> completely different.
Heh, for the experiment's sake I tried to define:
co=checkout --lightweight
alias and was curios what would happen.
Fortunately, bzr did the Right Thing :-)
So, now I see & understand that user aliases override built-in ones and
can live with that ;)
Shall we close this 'bug' as invalid?
Sincerely,
Gour
--
Gour | Zagreb, Croatia | GPG key: C6E7162D
----------------------------------------------------------------
>>>>> "Aaron" == Aaron Bentley <email address hidden> writes:
Hi Aaron,
Aaron> It's a feature. It keeps the model simple. It allows the
Aaron> aliases to vary independently. It allows the original command be
Aaron> given an alias, while an alias is created for the original name.
OK. I'm trying to adjust to the model...
Aaron> I don't think so. User aliases and built-in aliases are
Aaron> completely different.
Heh, for the experiment's sake I tried to define:
co=checkout --lightweight
alias and was curios what would happen.
Fortunately, bzr did the Right Thing :-)
So, now I see & understand that user aliases override built-in ones and
can live with that ;)
Shall we close this 'bug' as invalid?
Sincerely,
Gour
--
Gour | Zagreb, Croatia | GPG key: C6E7162D ------- ------- ------- ------- ------- ------- ------- ------- -
-------