From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] .gitignore: ignore output*
Date: Sat, 21 Oct 2017 16:04:04 +0200 [thread overview]
Message-ID: <20171021160404.579c29af@windsurf> (raw)
In-Reply-To: <20171021140108.24066-1-gael.portay@savoirfairelinux.com>
Hello,
On Sat, 21 Oct 2017 10:01:08 -0400, Ga?l PORTAY wrote:
> During development, it is often practical to have many output
> directories. The output directory is easily specified with O=<output>
> though is it useful to have a convention of 'output...' e.g.
> "output-rpi", "output-rpi2", and "output-rpi3-64".
>
> Signed-off-by: Ga?l PORTAY <gael.portay@savoirfairelinux.com>
> ---
> .gitignore | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.gitignore b/.gitignore
> index bb02d9f572..ec5768d053 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -1,4 +1,4 @@
> -/output
> +/output*
Not sure this is a good idea, it kind of makes an assumption on how
people would name their output directories.
If you're annoyed by your output directories, use make O=../output-rpi2
instead of make O=output-rpi2, and that's it :-)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-21 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 14:01 [Buildroot] [PATCH] .gitignore: ignore output* Gaël PORTAY
2017-10-21 14:04 ` Thomas Petazzoni [this message]
2017-10-21 18:16 ` Arnout Vandecappelle
2017-10-21 22:41 ` Gaël PORTAY
2017-10-21 22:40 ` Gaël PORTAY
2017-10-22 10:40 ` Arnout Vandecappelle
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=20171021160404.579c29af@windsurf \
--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