For the headers that appear in boost-root/boost, rather than a library specific subdirectory, it is very helpful if they self-identify what library they belong to. This allows scripts to associate the header with a library. The usual way to do this is to include a comment. A typical example: // See http://www.boost.org/libs/config for documentation The exact format doesn't matter. What does matter is that the library name be found somewhere in the file, immediately following a string which contains "/libs/". Below is the result of doing: grep -L "/libs/" *.h* I'd appreciate maintainers adding a library identifying comment to these files. Otherwise I'll do it, which carries a slight risk that I'll get it wrong. Thanks, --Beman aligned_storage.hpp asio.hpp bimap.hpp blank.hpp blank_fwd.hpp circular_buffer.hpp circular_buffer_fwd.hpp date_time.hpp dynamic_property_map.hpp foreach.hpp function_equal.hpp function_output_iterator.hpp get_pointer.hpp implicit_cast.hpp is_placeholder.hpp iterator_adaptors.hpp lexical_cast.hpp mpi.hpp non_type.hpp none.hpp none_t.hpp optional.hpp parameter.hpp pfto.hpp pointer_cast.hpp program_options.hpp smart_cast.hpp spirit.hpp state_saver.hpp strong_typedef.hpp thread.hpp type.hpp variant.hpp wave.hpp