From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] .gitignore: include common build sub-directories
Date: Tue, 14 Apr 2020 09:39:43 -0700 [thread overview]
Message-ID: <96a60b62-9558-0665-439a-1aacb3624fae@linaro.org> (raw)
In-Reply-To: <87v9m281vo.fsf@linaro.org>
On 4/14/20 9:31 AM, Alex Bennée wrote:
> Richard Henderson <richard.henderson@linaro.org> writes:
>> My build directories are always siblings of the source directory in the parent
>> directory.
>
>
> It's not exactly an un-common pattern - especially if you have a lot of
> build variants. Keeping them under builds makes it easier to blow the
> whole lot away rather than having a messy parent directory which you
> have to clean manually.
"Manual" is a bit of an overstatement. In the end there's no difference at
all: it's rm -rf build* no matter the $PWD where you perform it.
As for "messy", you're the one that put stuff that doesn't belong into the
source directory. Mine is nice and clean. ;-)
> Personally it also works better with my tooling which can slurp up all
> the build directories and present me with a menu of make commands to
> build from. That's not a good argument for accepting the patch though.
Hah.
r~
prev parent reply other threads:[~2020-04-14 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 16:29 [PATCH] .gitignore: include common build sub-directories Alex Bennée
2020-04-13 18:26 ` Eric Blake
2020-04-13 21:32 ` Alex Bennée
2020-04-13 21:42 ` Eric Blake
2020-04-13 21:45 ` Philippe Mathieu-Daudé
2020-04-14 8:00 ` Markus Armbruster
2020-04-14 8:47 ` Alex Bennée
2020-04-14 9:53 ` Philippe Mathieu-Daudé
2020-04-14 15:06 ` Richard Henderson
2020-04-14 16:31 ` Alex Bennée
2020-04-14 16:39 ` Richard Henderson [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=96a60b62-9558-0665-439a-1aacb3624fae@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
/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.