intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [maintainer-tools PATCH] dim: Properly handle series on apply_branch
Date: Fri, 18 Aug 2017 10:07:58 +0300	[thread overview]
Message-ID: <87pobt73qp.fsf@intel.com> (raw)
In-Reply-To: <20170817180950.7392-1-rodrigo.vivi@intel.com>

On Thu, 17 Aug 2017, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> So far we could use *dim* to apply a whole series
> in a mbox, but only the very last patch was receiving
> all the checks and patchwork link.
>
> So this patch remove this limitation by using git mailsplit
> to split the mbox and than use git am and checks individually
> on each patch.
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>  dim | 45 +++++++++++++++++++++++++--------------------
>  1 file changed, 25 insertions(+), 20 deletions(-)
>
> diff --git a/dim b/dim
> index 11aa675cc3bc..5457006631d6 100755
> --- a/dim
> +++ b/dim
> @@ -767,38 +767,43 @@ function dim_apply_branch
>  	branch=${1:?$usage}
>  	shift
>  	file=$(mktemp)
> +	dir=$(mktemp -d)
>  
>  	assert_branch $branch
>  	assert_repo_clean
>  
> +	committer_email=$(git_committer_email)
> +
>  	cat > $file
> +	git mailsplit -o$dir $file > /dev/null

Oh, git mailsplit must have been introduced after I looked into this the
last time. Nice.

The downside is that this doesn't work on patches piped from the MUA,
because git mailsplit expects an mbox. Fail.

I notice that you indent most of the function in the for loop, perhaps
that's an indication you should turn this one into a single patch
helper, and do the mailsplit in a new dim_apply_branch that only does
that?

>  
> -	message_id=$(message_get_id $file)
> +	for patch in `ls $dir`; do

Please use $(...) instead of `...`. Didn't test, but I think shellcheck
would complain.

I think you should do $(find $dir | sort) instead of ls.

Otherwise seems like this should work.

BR,
Jani.

>  
> -	committer_email=$(git_committer_email)
> +		message_id=$(message_get_id $dir/$patch)
>  
> -	patch_from=$(grep "From:" "$file" | head -1)
> -	if [[ "$patch_from" != *"$committer_email"* ]] ; then
> -		sob=-s
> -	fi
> +		patch_from=$(grep "From:" "$dir/$patch" | head -1)
> +		if [[ "$patch_from" != *"$committer_email"* ]] ; then
> +			sob=-s
> +		fi
>  
> -	git am --scissors -3 $sob "$@" $file
> +		git am --scissors -3 $sob "$@" $dir/$patch
>  
> -	if [ -n "$message_id" ]; then
> -		dim_commit_add_tag "Link: https://patchwork.freedesktop.org/patch/msgid/$message_id"
> -	else
> -		echoerr "WARNING: No message-id found in the patch file."
> -		rv=1
> -	fi
> +		if [ -n "$message_id" ]; then
> +			dim_commit_add_tag "Link: https://patchwork.freedesktop.org/patch/msgid/$message_id"
> +		else
> +			echoerr "WARNING: No message-id found in the patch file."
> +			rv=1
> +		fi
>  
> -	if ! checkpatch_commit HEAD; then
> -		rv=1
> -	fi
> -	if ! check_maintainer $branch HEAD; then
> -		rv=1
> -	fi
> +		if ! checkpatch_commit HEAD; then
> +			rv=1
> +		fi
> +		if ! check_maintainer $branch HEAD; then
> +			rv=1
> +		fi
>  
> -	eval $DRY $DIM_POST_APPLY_ACTION
> +		eval $DRY $DIM_POST_APPLY_ACTION
> +	done
>  
>  	return $rv
>  }

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-08-18  7:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 18:09 [maintainer-tools PATCH] dim: Properly handle series on apply_branch Rodrigo Vivi
2017-08-18  7:07 ` Jani Nikula [this message]
2017-08-19  0:05   ` Rodrigo Vivi
2017-08-21  8:01     ` Jani Nikula
2017-08-21 22:10       ` [PATCH] " Rodrigo Vivi
2017-08-22  7:22         ` Jani Nikula
2017-08-22 16:57           ` [maintainer-tools PATCH] " Rodrigo Vivi
2017-08-23  8:54             ` Jani Nikula
2017-08-23  8:58               ` Jani Nikula
2017-08-23 17:29                 ` Rodrigo Vivi
2017-08-24  7:58                   ` Jani Nikula
2017-08-22 16:58           ` [PATCH] " Rodrigo Vivi

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=87pobt73qp.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    /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 NNTP newsgroup(s).