From: Lukas Wunner <lukas@wunner.de>
To: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH maintainer-tools] dim: Replace git commit --amend from dim_apply with dimrc option
Date: Fri, 13 Nov 2015 16:34:07 +0100 [thread overview]
Message-ID: <20151113153407.GA23592@wunner.de> (raw)
In-Reply-To: <1447427109-5526-1-git-send-email-ander.conselvan.de.oliveira@intel.com>
Hi Ander,
On Fri, Nov 13, 2015 at 05:05:09PM +0200, Ander Conselvan de Oliveira wrote:
> Introduce DIM_POST_APPLY_ACTION to dimrc that allows the user to specify
> a command to be run after a patch is applied. Use eval so enviroment
> variables can be overriden with the option. For example:
>
> DIM_POST_APPLY_ACTION="EDITOR=\"gedit -w\" git commit --amend"
So an attacker wishing to smuggle a backdoor into the Linux kernel
only needs to find a way to modify that environment variable on
an Intel developers' machine.
If dim is invoked with $EDITOR set, this should be inherited to
child processes anyway, so it seems unnecessary to call eval.
Just my 2 cents,
Lukas
>
> Signed-off-by: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>
> ---
> dim | 2 +-
> dimrc.sample | 3 +++
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/dim b/dim
> index db92c57..b7c7ef7 100755
> --- a/dim
> +++ b/dim
> @@ -383,7 +383,7 @@ function dim_apply
> commit_add_tag "Link" "http://patchwork.freedesktop.org/patch/msgid/$message_id"
> fi
>
> - git commit --amend &
> + eval $DRY $DIM_POST_APPLY_ACTION
> }
>
> function magic_patch
> diff --git a/dimrc.sample b/dimrc.sample
> index 5687eaf..9f30cb2 100644
> --- a/dimrc.sample
> +++ b/dimrc.sample
> @@ -21,3 +21,6 @@
> # Mail User Agent supporting a subset of mutt(1) command line options:
> # [-s subject] [-i file] [-c cc-addr] to-addr [...]
> #DIM_MUA=mutt
> +
> +# Command to run after dim apply
> +#DIM_POST_APPLY_ACTION=git commit --amend
> --
> 2.4.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-11-13 15:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 12:05 [PATCH maintainer-tools] dim: Remove git commit --amend from dim_apply Ander Conselvan de Oliveira
2015-11-13 12:16 ` Chris Wilson
2015-11-13 12:31 ` Tvrtko Ursulin
2015-11-13 14:40 ` Ander Conselvan De Oliveira
2015-11-13 15:07 ` Tvrtko Ursulin
2015-11-13 15:11 ` Ander Conselvan De Oliveira
2015-11-18 15:51 ` Daniel Vetter
2015-11-13 12:33 ` Ander Conselvan De Oliveira
2015-11-13 12:42 ` Ville Syrjälä
2015-11-13 14:33 ` Jani Nikula
2015-11-13 14:42 ` Ville Syrjälä
2015-11-13 15:05 ` [PATCH maintainer-tools] dim: Replace git commit --amend from dim_apply with dimrc option Ander Conselvan de Oliveira
2015-11-13 15:34 ` Lukas Wunner [this message]
2015-11-13 15:36 ` Jani Nikula
2015-11-16 10:17 ` [PATCH v2 " Ander Conselvan de Oliveira
2015-11-18 15:52 ` Daniel Vetter
2015-11-19 8:22 ` Ander Conselvan De Oliveira
2018-12-17 14:49 ` ✗ Fi.CI.BAT: failure for dim: Remove git commit --amend from dim_apply Patchwork
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=20151113153407.GA23592@wunner.de \
--to=lukas@wunner.de \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=intel-gfx@lists.freedesktop.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