Remove the settings not more used
Bug #1248153 reported by
Marco Giusti
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Virtualbricks |
Invalid
|
Low
|
Marco Giusti |
Bug Description
The settings window contains settings that are not used anymore. Ex:
- X-window terminal command. Now xterm is always used because of the different options of each terminal
- Private COW format. This is still used but the other parts of virtualbricks assume that the format is qcow2
Remove that parts from the settings window.
Changed in virtualbrick: | |
importance: | Medium → Low |
assignee: | nobody → mg (marco-giusti) |
Changed in virtualbrick: | |
status: | New → Invalid |
To post a comment you must log in.
I think it's better to leave the user the option to choose which kind of
private cow he wants to use.
Il 05/nov/2013 13:20 "mg" <email address hidden> ha scritto:
> Public bug reported: /bugs.launchpad .net/bugs/ 1248153 /bugs.launchpad .net/virtualbri ck/+bug/ 1248153/ +subscriptions
>
> The settings window contains settings that are not used anymore. Ex:
>
> - X-window terminal command. Now xterm is always used because of the
> different options of each terminal
>
> - Private COW format. This is still used but the other parts of
> virtualbricks assume that the format is qcow2
>
> Remove that parts from the settings window.
>
> ** Affects: virtualbrick
> Importance: Medium
> Status: New
>
>
> ** Tags: interface-cleanup
>
> --
> You received this bug notification because you are subscribed to
> Virtualbricks.
> https:/
>
> Title:
> Remove the settings not more used
>
> Status in Virtualbricks:
> New
>
> Bug description:
> The settings window contains settings that are not used anymore. Ex:
>
> - X-window terminal command. Now xterm is always used because of the
> different options of each terminal
>
> - Private COW format. This is still used but the other parts of
> virtualbricks assume that the format is qcow2
>
> Remove that parts from the settings window.
>
> To manage notifications about this bug go to:
> https:/
>