All of lore.kernel.org
 help / color / mirror / Atom feed
From: "William A. Kennington III" <wak@google.com>
To: openembedded-core@lists.openembedded.org
Cc: "William A. Kennington III" <wak@google.com>
Subject: [PATCH] kernel: Commit without running hooks
Date: Wed, 25 Oct 2023 15:37:10 -0700	[thread overview]
Message-ID: <20231025223710.93502-1-wak@google.com> (raw)

The hooks are pulled from the impure environment and are often broken in
our environments. There is no reason to add extra metadata or verify the
commit message as its arbitrary to turn the tarball into a git repo.

Signed-off-by: William A. Kennington III <wak@google.com>
---
 meta/classes-recipe/kernel-yocto.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes-recipe/kernel-yocto.bbclass b/meta/classes-recipe/kernel-yocto.bbclass
index 4ac977b122..cb9cd26b09 100644
--- a/meta/classes-recipe/kernel-yocto.bbclass
+++ b/meta/classes-recipe/kernel-yocto.bbclass
@@ -408,7 +408,7 @@ do_kernel_checkout() {
 		git init
 		check_git_config
 		git add .
-		git commit -q -m "baseline commit: creating repo for ${PN}-${PV}"
+		git commit -q -n -m "baseline commit: creating repo for ${PN}-${PV}"
 		git clean -d -f
 	fi
 
-- 
2.42.0.820.g83a721a137-goog



             reply	other threads:[~2023-10-25 22:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 22:37 William A. Kennington III [this message]
2023-10-26  2:07 ` [OE-core] [PATCH] kernel: Commit without running hooks Bruce Ashfield
2023-10-26 10:38   ` William Kennington
2023-10-26 14:25     ` Bruce Ashfield
2023-10-27 23:27       ` Peter Kjellerstedt
2023-10-28 12:32         ` Bruce Ashfield
     [not found]         ` <1792457740E31CAD.7262@lists.openembedded.org>
2023-10-28 12:56           ` Bruce Ashfield
2023-10-27 10:08 ` Luca Ceresoli
2023-10-27 21:44   ` William Kennington

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=20231025223710.93502-1-wak@google.com \
    --to=wak@google.com \
    --cc=openembedded-core@lists.openembedded.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.