Attachment 45377 Details for Bug 34870 – specification: fix versioning

[patch] specification: fix versioning

0005-specification-fix-versioning.patch (text/plain), 1.37 KB, created by Simon McVittie on 2011-04-07 07:30:08 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2011-04-07 07:30:08 UTC

Size: 1.37 KB

patch

obsolete

>From 976b7a7956d40844c5b61d8cec352bec8f93d72f Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Thu, 7 Apr 2011 14:46:04 +0100
>Subject: [PATCH 5/7] specification: fix versioning
>
>We've added things since 0.15, so this isn't still 0.15.
>---
> doc/dbus-specification.xml |    8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
>diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
>index 63146bb..8d631ae 100644
>--- a/doc/dbus-specification.xml
>+++ b/doc/dbus-specification.xml
>@@ -6,8 +6,8 @@
> <article id="index">
>   <articleinfo>
>     <title>D-Bus Specification</title>
>-    <releaseinfo>Version 0.15</releaseinfo>
>-    <date>3 November 2010</date>
>+    <releaseinfo>Version 0.16</releaseinfo>
>+    <date>(not finalized)</date>
>     <authorgroup>
>       <author>
> 	<firstname>Havoc</firstname>
>@@ -3757,9 +3757,9 @@
>                     </para>
>                     <para>
>                       <emphasis>
>-                        This match key was added in version 0.15 of the
>+                        This match key was added in version 0.16 of the
>                         D-Bus specification and implemented by the bus
>-                        daemon in dbus 1.4.7 and later.
>+                        daemon in dbus 1.5.0 and later.
>                       </emphasis>
>                     </para>
>                 </entry>
>-- 
>1.7.4.1
>

Actions: View | Splinter Review

Attachments on bug 34870: 44235 | 45376 | 45377 | 45382 | 45384 | 45385

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.