Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] manual: do not track generated files
Date: Mon, 25 Mar 2013 09:32:29 +0100	[thread overview]
Message-ID: <20130325093229.4ea7044b@skate> (raw)
In-Reply-To: <514FF950.4080307@mind.be>

Dear Arnout Vandecappelle,

On Mon, 25 Mar 2013 08:14:24 +0100, Arnout Vandecappelle wrote:

>   If they are not committed, they shouldn't be in the buildroot tree. 
> Instead they should move to output/docs/manual/...
> 
>   Or is asciidoc making that hard?

Yes, we already discussed that with Samuel yesterday, and he has pushed
to his branch a new version that generates the files in $(O). It's not
entirely pretty though because asciidoc cannot include .txt files from
multiple directories, so we have to copy all the static .txt files to
somewhere in $(O) so that they can be in the same directory as the
generated .txt files.

Yann has sent a patch set that includes Samuel changes, see:

From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: buildroot at busybox.net
Subject: [Buildroot] [PATCH 07/14] manual: do not track generated files
Date: Sun, 24 Mar 2013 23:50:42 +0100

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-03-25  8:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 20:12 [Buildroot] [PATCH 6/6] manual: do not track generated files Samuel Martin
2013-03-25  7:14 ` Arnout Vandecappelle
2013-03-25  8:32   ` Thomas Petazzoni [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130325093229.4ea7044b@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox