From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Théo Lebrun via buildroot" <buildroot@buildroot.org>
Cc: "Théo Lebrun" <theo.lebrun@bootlin.com>
Subject: Re: [Buildroot] [PATCH] gitignore: ignore utils/brmake log output named `br.log`
Date: Thu, 1 Jan 2026 14:27:37 +0100 [thread overview]
Message-ID: <20260101142737.0c8644b4@windsurf> (raw)
In-Reply-To: <20251117-gitignore-brmake-log-v1-1-a77ec4bb1db2@bootlin.com>
On Mon, 17 Nov 2025 18:07:52 +0100
Théo Lebrun via buildroot <buildroot@buildroot.org> wrote:
> The `utils/brmake` tool runs `make all` with logs put into `br.log`.
> That file is therefore the result of a build and committing it never
> makes sense, neither upstream nor on any other remote/branch.
>
> ⟩ git status --short
> ⟩ make beaglebone_defconfig
> ⟩ ./utils/brmake
> ⟩ git status --short
> ?? br.log
>
> Add a new `/br.log` entry in the root `.gitignore` file.
> Append to the end because no ordering logic was found.
>
> Signed-off-by: Théo Lebrun <theo.lebrun@bootlin.com>
> ---
> .gitignore | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-01 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 17:07 [Buildroot] [PATCH] gitignore: ignore utils/brmake log output named `br.log` Théo Lebrun via buildroot
2026-01-01 13:27 ` Thomas Petazzoni via buildroot [this message]
2026-01-13 19:45 ` Arnout Vandecappelle via buildroot
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=20260101142737.0c8644b4@windsurf \
--to=buildroot@buildroot.org \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
/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.