Alexander Belchenko wrote:
> Ian Clatworthy пишет:
>> Public bug reported:
>>
>> Given a project hosted at lp:xxx and a local feature branch called yyy,
>> qpush could suggest a sensible push location when one is yet to be
>> defined, namely lp:~lp-user-id/xxx/yyy. I'm happy to add this at the
>> Explorer layer but it would be generally useful for other qbzr-based UIs
>> (like TortoiseBzr) so I'd prefer to see it at the qbzr layer.
>
> And how you see it can be done? How qbzr will know name of the project?
> The launchpad user name available in bazaar.conf.
>
Taking an explorer feature branch as an example:
* parent branch is ../trunk/
* the parent branch of ../trunk/ is
bzr+ssh://bazaar.launchpad.net/~bzr-explorer-dev/bzr-explorer/trunk/.
That pattern is highly predictable I believe. In general:
* if the parent branch is ../xxx AND
* it's parent is bzr+ssh://bazaar.launchpad.net/~owner/ppp/whatever/
Alexander Belchenko wrote:
> Ian Clatworthy пишет:
>> Public bug reported:
>>
>> Given a project hosted at lp:xxx and a local feature branch called yyy,
>> qpush could suggest a sensible push location when one is yet to be
>> defined, namely lp:~lp-user-id/xxx/yyy. I'm happy to add this at the
>> Explorer layer but it would be generally useful for other qbzr-based UIs
>> (like TortoiseBzr) so I'd prefer to see it at the qbzr layer.
>
> And how you see it can be done? How qbzr will know name of the project?
> The launchpad user name available in bazaar.conf.
>
Taking an explorer feature branch as an example:
* parent branch is ../trunk/ //bazaar. launchpad. net/~bzr- explorer- dev/bzr- explorer/ trunk/.
* the parent branch of ../trunk/ is
bzr+ssh:
That pattern is highly predictable I believe. In general:
* if the parent branch is ../xxx AND //bazaar. launchpad. net/~owner/ ppp/whatever/
* it's parent is bzr+ssh:
then the project is ppp.
Ian C.