From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Jonas Rebmann <jre@pengutronix.de>
Subject: Re: [PATCH v2] gitignore: ignore /build, /oe-logs, /oe-workdir
Date: Thu, 30 Oct 2025 14:13:12 +0100 [thread overview]
Message-ID: <176182999262.2297613.14996962564252896621.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20251030-gitignore-build-v2-1-8f4fcd824921@pengutronix.de>
On Thu, 30 Oct 2025 09:41:00 +0100, Jonas Rebmann wrote:
> Documentation such as Documentation/boards/kvx.rst and tooling such as
> conftest.py suggests /build is a good choice for build output directory.
> The build system does set up a .gitignore in the build directory but
> this has no effect if /build is a symlink to outside the tree.
>
> Similarly, YOCTOs "devtool" sets up the symlinks /oe-logs and
> /oe-workdir to point to the respective paths in yoctos build tree.
>
> [...]
Applied, thanks!
[1/1] gitignore: ignore /build, /oe-logs, /oe-workdir
https://git.pengutronix.de/cgit/barebox/commit/?id=542520c8db31 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-10-30 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 8:41 Jonas Rebmann
2025-10-30 8:43 ` Jonas Rebmann
2025-10-30 13:13 ` Sascha Hauer [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=176182999262.2297613.14996962564252896621.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jre@pengutronix.de \
/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