Backports Archive mirror
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: backports@vger.kernel.org
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Subject: [PATCH 1/2] backports-update-manager: Add option to not update git trees
Date: Mon, 22 Jan 2024 22:36:48 +0100	[thread overview]
Message-ID: <20240122213649.149703-1-hauke@hauke-m.de> (raw)

Add the '--no-git-update which will deactivate updating the git trees.
This can be used in the github actions.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
---
 devel/backports-update-manager | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/devel/backports-update-manager b/devel/backports-update-manager
index 9177be76..815a0421 100755
--- a/devel/backports-update-manager
+++ b/devel/backports-update-manager
@@ -629,6 +629,8 @@ def _main():
     parser.add_argument('--reference', metavar='<path-to-git-obj-dir>', type=str,
                         default=None,
                         help='Override what argument to use to git clone --reference')
+    parser.add_argument('--no-git-update', const=True, default=False, action="store_const",
+                        help='Don\'t update git trees')
     args = parser.parse_args()
 
     bk_updater = backport_kernel_updater(yes=args.yes or args.force,
@@ -649,7 +651,8 @@ def _main():
     bk_updater.remove_stale_kernel_dirs()
     bk_updater.get_backport_pkgs()
     bk_updater.extract_backport_pkgs()
-    bk_updater.update_git_trees()
+    if not args.no_git_update:
+        bk_updater.update_git_trees()
 
     return 0
 
-- 
2.43.0


             reply	other threads:[~2024-01-22 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 21:36 Hauke Mehrtens [this message]
2024-01-22 21:36 ` [PATCH 2/2] github: Add github action to test build Hauke Mehrtens

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=20240122213649.149703-1-hauke@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=backports@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).