Bazaar GTK+ Frontends

Don't ask about setting default push location

Bug #151818 reported by Jeff Fortin Tam
6
Affects Status Importance Assigned to Milestone
Bazaar GTK+ Frontends
Fix Released
Low
Jasper Groenewegen

Bug Description

When pushing, I get this dialog:

<big>Set default push location</big>
There is no default push location set.
Set 'bzr+ssh://<email address hidden>/~kiddo/specto/specto-jeff' as default now?
[no] [yes]

There is a usability bug with this. I am not very familiar with VCS user interfaces, and I am a bit uncertain of steps I take, so each time something is explained clearly, it helps me :)

The problem I see here is that it asks for making the push location the default... but default for what? Do you mean the default *system-wide* (or at least user-wide)? Or just default for this particular folder? I'd like to have this information in the dialog.

Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 151818] Re: default push location dialog unclear

I don't think we should ask, but just GFD. There is no disadvantage when
doing this.

 summary "Don't ask about setting default push location"
 status triaged
 importance low
--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>

Changed in bzr-gtk:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

I agree that not asking at all would simplify the UI, code and interactions. A user can expect the thing to remember the last push location.

Changed in olive:
status: New → Invalid
Changed in bzr-gtk:
status: Triaged → Confirmed
Revision history for this message
Jasper Groenewegen (colbrac) wrote :

Patch that removes question send to BB (http://bundlebuggy.aaronbentley.com/project/bzr-gtk/request/%<email address hidden>%3E)

Changed in bzr-gtk:
status: Confirmed → In Progress
Revision history for this message
Jasper Groenewegen (colbrac) wrote : Re: [MERGE] Remove question to set default pushlocation when None set yet. Users would expect this to be set anyway. Fixes LP:151818

On second thought.. should there be a checkbox 'Set as default'?
If you mess up the first attempt for a push location now, it will always
reappear as there is no other way to set the push location for a branch
through olive/bzr-gtk that I know of.

Jasper

Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 151818] Re: [MERGE] Remove question to set default pushlocation when None set yet. Users would expect this to be set anyway. Fixes LP:151818

On Tue, Jul 22, 2008 at 09:52:49AM -0000, Jasper Groenewegen wrote:
> On second thought.. should there be a checkbox 'Set as default'?
> If you mess up the first attempt for a push location now, it will always
> reappear as there is no other way to set the push location for a branch
> through olive/bzr-gtk that I know of.
 I think it would be sensible to only set the push location if the push
was successful. AFAIK that's what bzr itself does too.

Cheers,

Jelmer

Revision history for this message
Jasper Groenewegen (colbrac) wrote :

Fix merged in rev 562

Changed in bzr-gtk:
assignee: nobody → colbrac
status: In Progress → Fix Committed
Jelmer Vernooij (jelmer)
Changed in bzr-gtk:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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