From: Tom Rini <trini@konsulko.com>
To: Raymond Mao <raymond.mao@linaro.org>
Cc: u-boot@lists.denx.de, sumit.garg@linaro.org,
jerome.forissier@linaro.org, Simon Glass <sjg@chromium.org>,
Paul Barker <paul.barker.ct@bp.renesas.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH v2] tools: Add script to update git subtree projects
Date: Mon, 22 Jul 2024 19:55:25 -0600 [thread overview]
Message-ID: <20240723015525.GC989285@bill-the-cat> (raw)
In-Reply-To: <20240722193052.57592-1-raymond.mao@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
On Mon, Jul 22, 2024 at 12:30:50PM -0700, Raymond Mao wrote:
> Recently we are introducing multiple git subtree projects and
> it is the right time to have a universal script to update
> various subtrees and replace the dts/update-dts-subtree.sh.
>
> update-subtree.sh is a wrapper of git subtree commands.
>
> Usage: From U-Boot top directory,
> run
> $ ./tools/update-subtree.sh pull <subtree-name> <release-tag>
> for pulling a tag from the upstream.
> Or run
> $ ./tools/update-subtree.sh pick <subtree-name> <commit-id>
> for cherry-pick a commit from the upstream.
>
> Currently <subtree-name> supports dts, mbedtls and lwip.
>
> Signed-off-by: Raymond Mao <raymond.mao@linaro.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-07-23 1:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 19:30 [PATCH v2] tools: Add script to update git subtree projects Raymond Mao
2024-07-22 19:38 ` Jerome Forissier
2024-07-23 1:55 ` Tom Rini [this message]
2024-07-23 6:45 ` Ilias Apalodimas
2024-07-23 7:16 ` Quentin Schulz
2024-07-23 14:05 ` Raymond Mao
2024-07-23 14:18 ` Quentin Schulz
2024-07-24 7:08 ` Sumit Garg
2024-07-24 14:10 ` Raymond Mao
2024-07-25 5:45 ` Sumit Garg
2024-07-25 7:09 ` Jerome Forissier
2024-07-25 13:39 ` Raymond Mao
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=20240723015525.GC989285@bill-the-cat \
--to=trini@konsulko.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=paul.barker.ct@bp.renesas.com \
--cc=quentin.schulz@cherry.de \
--cc=raymond.mao@linaro.org \
--cc=sjg@chromium.org \
--cc=sumit.garg@linaro.org \
--cc=u-boot@lists.denx.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