mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 4/6] scripts/dtc: mention dtc project in update-dtc-source.sh commit message
Date: Mon, 23 Sep 2019 15:49:05 +0200	[thread overview]
Message-ID: <20190923134905.eam54zy66hb74ujc@pengutronix.de> (raw)
In-Reply-To: <20190923121018.31574-5-a.fatoum@pengutronix.de>

On Mon, Sep 23, 2019 at 02:10:16PM +0200, Ahmad Fatoum wrote:
> update-dtc-source.sh generates the commit message after it runs
> to completion. The word upstream is often used to refer to the
> Linux kernel within barebox, so change the wording to refer
> explicitly to dtc upstream.
> 
> Cc: Roland Hieber <r.hieber@pengutronix.de>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>

Acked-by: Roland Hieber <rhi@pengutronix.de>

 :)


> ---
>  scripts/dtc/update-dtc-source.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/scripts/dtc/update-dtc-source.sh b/scripts/dtc/update-dtc-source.sh
> index 0a098df710c3..604ed254f542 100755
> --- a/scripts/dtc/update-dtc-source.sh
> +++ b/scripts/dtc/update-dtc-source.sh
> @@ -72,7 +72,7 @@ git add ./libfdt/libfdt.h
>  commit_msg=$(cat << EOF
>  scripts/dtc: Update to upstream version ${dtc_version}
>  
> -This adds the following commits from upstream:
> +This adds the following commits from upstream dtc:
>  
>  ${dtc_log}
>  EOF
> -- 
> 2.23.0
> 
> 

-- 
Roland Hieber                     | r.hieber@pengutronix.de     |
Pengutronix e.K.                  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2019-09-23 13:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23 12:10 [PATCH 0/6] scripts/dtc: rework dtc import handling Ahmad Fatoum
2019-09-23 12:10 ` [PATCH 1/6] scripts/dtc: Reinstate barebox-specifics in update-dtc-source.sh Ahmad Fatoum
2019-09-23 12:10 ` [PATCH 2/6] scripts/dtc: reinstate building of fdtget along with dtc Ahmad Fatoum
2019-09-23 12:10 ` [PATCH 3/6] scripts/dtc: git rm old files as part of update process Ahmad Fatoum
2019-09-23 12:10 ` [PATCH 4/6] scripts/dtc: mention dtc project in update-dtc-source.sh commit message Ahmad Fatoum
2019-09-23 13:49   ` Roland Hieber [this message]
2019-09-23 12:10 ` [PATCH 5/6] scripts/dtc: Update to upstream version v1.5.1 Ahmad Fatoum
2019-09-23 12:10 ` [PATCH 6/6] Documentation: document barebox device tree handling Ahmad Fatoum
2019-09-25  9:51 ` [PATCH 0/6] scripts/dtc: rework dtc import handling 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=20190923134905.eam54zy66hb74ujc@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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