mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jonas Rebmann <jre@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
	 BAREBOX <barebox@lists.infradead.org>
Cc: Jonas Rebmann <jre@pengutronix.de>
Subject: [PATCH v2] gitignore: ignore /build, /oe-logs, /oe-workdir
Date: Thu, 30 Oct 2025 09:41:00 +0100	[thread overview]
Message-ID: <20251030-gitignore-build-v2-1-8f4fcd824921@pengutronix.de> (raw)

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.

Include those in .gitignore.

Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
---
Changes in v2:
- EDITME: describe what is new in this series revision.
- EDITME: use bulletpoints and terse descriptions.
- Link to v1: https://lore.barebox.org/barebox/20251017-gitignore-build-v1-1-f25d35c3bff4@pengutronix.de
---
 .gitignore | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.gitignore b/.gitignore
index 98bb4dac89..a235f9f7de 100644
--- a/.gitignore
+++ b/.gitignore
@@ -53,6 +53,9 @@ policy-list
 /TAGS
 /barebox*
 /System.map
+/build
+/oe-logs
+/oe-workdir
 
 #
 # git files that we don't want to ignore even it they are dot-files

---
base-commit: 8defba1d0ab1aef9dd5d57710e18d0d02e2c48e2
change-id: 20251017-gitignore-build-d90cb643b130

Best regards,
--  
Jonas Rebmann <jre@pengutronix.de>




             reply	other threads:[~2025-10-30  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30  8:41 Jonas Rebmann [this message]
2025-10-30  8:43 ` Jonas Rebmann
2025-10-30 13:13 ` Sascha Hauer

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=20251030-gitignore-build-v2-1-8f4fcd824921@pengutronix.de \
    --to=jre@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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