From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] ptxdist: Add --silent and -s as aliases for --quiet
Date: Wed, 19 Oct 2022 07:41:05 +0200 [thread overview]
Message-ID: <20221019054105.401702-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220930143637.3372940-1-u.kleine-koenig@pengutronix.de>
Thanks, applied as 120c9ba1be73e425b9de3012ac5e9eec1fd0ea07.
Michael
[sent from post-receive hook]
On Wed, 19 Oct 2022 07:41:05 +0200, Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> Many options that ptxdist parses are the same for make(1) (e.g. -j, -k,
> -d). However the option to make make silent is -s, add that to reduce
> the time I spend on thinking which option is for which command.
>
> While at it also add --silent in accordance to make (which also knows
> about --quiet by the way).
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> Message-Id: <20220930143637.3372940-1-u.kleine-koenig@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/bin/ptxdist b/bin/ptxdist
> index 5c6df104e5f6..dfb619cbd8d0 100755
> --- a/bin/ptxdist
> +++ b/bin/ptxdist
> @@ -812,6 +812,7 @@ Options:
>
> --debug, -d print out additional info (like make decisions)
> --quiet, -q suppress output, show only stderr
> + --silent, -s alias for --quiet
> --verbose, -v be more verbose, print command before execute them
> --output-sync Improve output readability for parallel building.
> Disabled by default except for quiet builds.
> @@ -1148,7 +1149,7 @@ parse_first()
> --progress)
> PTXDIST_PROGRESS=1
> ;;
> - -q|--quiet)
> + -q|--quiet|-s|--silent)
> PTXDIST_QUIET=1
> ;;
> --git)
prev parent reply other threads:[~2022-10-19 5:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 14:36 [ptxdist] [PATCH] " Uwe Kleine-König
2022-10-19 5:41 ` Michael Olbrich [this message]
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=20221019054105.401702-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.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