Hard to branch into a subdirectory

Bug #253063 reported by Dan Watkins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Low
Unassigned

Bug Description

Neither
    $ bzr branch pyblosxom.old/pyblosxom-upstream/ upstreams/
nor
    $ bzr branch pyblosxom.old/pyblosxom-upstream/ upstreams
allow me to branch pyblosxom.old/pyblosxom-upstream/ into upstreams/pyblosxom-upstreams. I have to do
    $ bzr branch pyblosxom.old/pyblosxom-upstream upstreams/pyblosxom-upstream

This is irritating, because I then have to check the new name for typos.

Tags: easy ui
Dan Watkins (oddbloke)
Changed in bzr:
importance: Undecided → Low
status: New → Confirmed
status: Confirmed → New
Revision history for this message
James Westby (james-w) wrote :

Hi,

"upstreams" already exists I assume?

The only argument I could see against this is that the user
would be surprised if they didn't expect "upstreams" to exist,
and intended that to be the branch, but it's not irrecoverable,
so I don't think it would be a problem.

Thanks,

James

Changed in bzr:
status: New → Confirmed
Revision history for this message
John A Meinel (jameinel) wrote :

Well, you can also do "cd upstreams && bzr branch ../pyblosxom.old/pyblosxom-upstream".

Alternatively we could support "bzr branch -d upstreams pyblosxom.o....", though that is a slightly different of a meaning of -d than we usually have.

Revision history for this message
Robert Collins (lifeless) wrote :

That -d usage seems consistent - do the operation in the upstreams directory.

Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
Jelmer Vernooij (jelmer)
tags: removed: check-for-breezy
Changed in brz:
status: New → Triaged
importance: Undecided → Low
no longer affects: brz
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.