From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] manual: do not track generated files
Date: Mon, 25 Mar 2013 08:14:24 +0100 [thread overview]
Message-ID: <514FF950.4080307@mind.be> (raw)
In-Reply-To: <1363983159-4357-1-git-send-email-s.martin49@gmail.com>
On 22/03/13 21:12, Samuel Martin wrote:
> Since there is no need to edit the generated list, we don't need
> to keep these files under git control, so:
> * remove existing lists
> * add the 3 generated lists to .gitignore
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?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-03-25 7:14 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 [this message]
2013-03-25 8:32 ` Thomas Petazzoni
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=514FF950.4080307@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.