I am happy to announce a new release of virt-viewer, version 0.5.5.
This is primarily a bugfix release
http://virt-manager.org/download/sources/virt-viewer/virt-viewer-0.5.5.tar.gz
Signed with key DAF3 A6FD B26B 6291 2D0E 8E3F BE86 EBB4 1510 4FDF (4096R)
http://virt-manager.org/download/s
On 13.02.2013 16:05, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> Rather than trying to manually keep track of authors,
> just auto-generate the list from GIT logs
>
> Signed-off-by: Daniel P. Berrange
> ---
> AUTHORS | 77
> -
From: "Daniel P. Berrange"
Rather than trying to manually keep track of authors,
just auto-generate the list from GIT logs
Signed-off-by: Daniel P. Berrange
---
AUTHORS | 77
AUTHORS.in | 21 +
Makefile.am | 1
Hi
- Mensaje original -
> > + - Fixes rhbz #856610, #856678, #864929, #864033, #875697,
> > #881020,
> > +#843410, #803912, #903190
>
> Upstream releases shouldn't refer to downstream distro bugs, so I'll
> remove all these.
What is the upstream bug tracker for virt-viewer?
> Pleas
On Wed, Feb 13, 2013 at 01:54:46PM +0100, Marc-André Lureau wrote:
> ---
> NEWS | 16
> configure.ac | 2 +-
> 2 files changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/NEWS b/NEWS
> index 47e23f6..3c8b18f 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -1,6 +1,22 @@
>
Hi Jegan,
To the best of my knowledge and from what I could grab from virt-top
manual page, there is no way of including the current date in virt-top
output. The purpose of virt-top is to show an instantaneous picture of
the virtual-machine states. That's why the date is not shown: the date
o
---
NEWS | 16
configure.ac | 2 +-
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index 47e23f6..3c8b18f 100644
--- a/NEWS
+++ b/NEWS
@@ -1,6 +1,22 @@
Virt Viewer News
+0.5.5: Feb 13, 2013
+---
+
+ - I
On Wed, Feb 13, 2013 at 12:45:31PM +0100, Marc-André Lureau wrote:
> In order to build the MSI, you will need msitools:
> http://ftp.gnome.org/pub/GNOME/sources/msitools/
>
> The MANUFACTURER environment variable is mandatory and should be set
> to the manufacturer/author of the MSI build.
Not a
In order to build the MSI, you will need msitools:
http://ftp.gnome.org/pub/GNOME/sources/msitools/
The MANUFACTURER environment variable is mandatory and should be set
to the manufacturer/author of the MSI build.
---
configure.ac| 1 +
data/Makefile.am| 19 +-
data/v
- Mensaje original -
> On Tue, Feb 12, 2013 at 06:47:27PM +0100, Marc-André Lureau wrote:
> > On Tue, Feb 12, 2013 at 6:36 PM, Christophe Fergeau
> > wrote:
> > > Looks much better, but one of my comments in the previous review
> > > is still
> > > pending.
> >
> > About the info string
On Tue, Feb 12, 2013 at 06:47:27PM +0100, Marc-André Lureau wrote:
> On Tue, Feb 12, 2013 at 6:36 PM, Christophe Fergeau
> wrote:
> > Looks much better, but one of my comments in the previous review is still
> > pending.
>
> About the info string "consistency"? Red Hat vs spice-space.org ?
>
>
11 matches
Mail list logo
