Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 3D1B2431FD5 for ; Sat, 11 Jan 2014 16:12:20 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxz0o7IaHJXV for ; Sat, 11 Jan 2014 16:12:16 -0800 (PST) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 18E48431FC3 for ; Sat, 11 Jan 2014 16:12:16 -0800 (PST) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1W28ex-0006fP-3k; Sat, 11 Jan 2014 20:12:11 -0400 Received: (nullmailer pid 8028 invoked by uid 1000); Sun, 12 Jan 2014 00:12:07 -0000 From: David Bremner To: Tomi Ollila , Jani Nikula , notmuch@notmuchmail.org Subject: Re: [PATCH v2 0/2] doxygen generated library reference man page In-Reply-To: References: <87bnzq605g.fsf@zancas.localnet> User-Agent: Notmuch/0.17+16~gd4acd22 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Sat, 11 Jan 2014 20:12:07 -0400 Message-ID: <87zjn2ys6g.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jan 2014 00:12:20 -0000 Tomi Ollila writes: > > IMO "install" target should not execute anything that is located in > 'devel/' (i.e. build should be "devel/" -free) so IMO the doxygen.cfg > should be moved to some other directory > (but where? to the root? to man/* to upcoming info/*?) > Since we're bikeshedding, what about a top level "doc" directory, with man, info, etc... underneath Assuming this info thing goes anywhere. d