Your message dated Sun, 18 May 2014 23:31:57 -0500
with message-id <[email protected]>
and subject line closing: as-designed
has caused the Debian Bug report #574670,
regarding libboost-doc: Please document that the MPL -> Fusion adapter also 
works the other way.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
574670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574670
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libboost-doc
Version: 1.40.0.1
Severity: minor

  In the section "mpl sequence", the Fusion documentation states that:

    Including the module header makes all MPL sequences fully
    conforming fusion sequences.

  In fact, it works the other way around as well, turning Fusion
sequences into MPL sequences.  Even something as simple as adding
"... and all fusion sequences fully conforming MPL sequences" would
have saved me some effort trying to find out how to do this.

  Daniel

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libboost-doc depends on:
ii  libboost1.40-doc              1.40.0-6   Boost.org libraries documentation

libboost-doc recommends no packages.

libboost-doc suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
The upstream view is that "Fusion sequences are always conforming mpl
sequences"; see https://svn.boost.org/trac/boost/ticket/4029

If you can improve the wording, please respond to the above boost ticket.

Thanks,
-Steve

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to