All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: David Miller <davem@davemloft.net>,
	jiri@resnulli.us, sfr@canb.auug.org.au, netdev@vger.kernel.org,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	andrew@lunn.ch
Subject: Re: linux-next: Fixes tag needs some work in the net-next tree
Date: Thu, 21 Feb 2019 11:04:09 +0530	[thread overview]
Message-ID: <20190221053409.GH2736@vkoul-mobl> (raw)
In-Reply-To: <20190220205910.7bd7fd40@redhat.com>

On 20-02-19, 20:59, Stefano Brivio wrote:
> On Wed, 20 Feb 2019 11:02:01 -0800 (PST)
> David Miller <davem@davemloft.net> wrote:
> 
> > From: Jiri Pirko <jiri@resnulli.us>
> > Date: Wed, 20 Feb 2019 09:36:11 +0100
> > 
> > > Would be good to have some robot checking "Fixes" sanity...  
> > 
> > I want to add a script to my trees that locally do it for me but the
> > backlog for patch review for me is so huge that I never get to "fun"
> > tasks like that....
> 
> If it helps, this is what I use after being bitten once:
> 
> #!/bin/sh
> 
> [ ${#} -ne 2 ] && echo "Usage: %0 PATCH_FILE GIT_TREE" && exit 1
> grep "^Fixes: " "${1}" | while read -r f; do
> 	sha="$(echo "${f}" | cut -d' ' -f2)"
> 	if [ -z "${sha}" ] || [ "${f}" != "$(git -C "${2}" show -s --abbrev=12 --pretty=format:"Fixes: %h (\"%s\")" "${sha}" 2>/dev/null)" ]; then
> 		echo "Bad tag: ${f}" && exit 1
> 	fi
> done

Awesome thanks, I am adding this into my patch commit script and well as
send script

-- 
~Vinod

  parent reply	other threads:[~2019-02-21  5:34 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 22:31 linux-next: Fixes tag needs some work in the net-next tree Stephen Rothwell
2019-02-20  4:40 ` Vinod Koul
2019-02-20  5:38   ` Stephen Rothwell
2019-02-20  6:48   ` David Miller
2019-02-20  8:36     ` Jiri Pirko
2019-02-20 19:02       ` David Miller
2019-02-20 19:58         ` Jiri Pirko
2019-02-20 20:25           ` David Miller
2019-02-20 20:26             ` Jiri Pirko
2019-02-20 19:59         ` Stefano Brivio
2019-02-20 20:25           ` David Miller
2019-02-20 20:37             ` Stefano Brivio
2019-02-20 20:42               ` David Miller
2019-02-21  5:34           ` Vinod Koul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-26 21:37 Stephen Rothwell
2021-08-16 22:04 Stephen Rothwell
2021-08-17  7:53 ` Nikolay Aleksandrov
2021-04-18 21:53 Stephen Rothwell
2021-03-30  1:15 Stephen Rothwell
2021-03-26 23:03 Stephen Rothwell
2020-09-15 23:04 Stephen Rothwell
2020-06-01 23:12 Stephen Rothwell
2020-06-02  7:31 ` Ayush Sawal
2020-06-02 10:18   ` Stephen Rothwell
2020-06-02 10:30     ` Ayush Sawal
2020-04-22 22:16 Stephen Rothwell
2020-02-27  4:42 Stephen Rothwell
2020-02-27  9:01 ` Maxim Mikityanskiy
2020-02-17  4:23 Stephen Rothwell
2019-12-18  6:35 Stephen Rothwell
2019-11-04 21:01 Stephen Rothwell
2019-09-10 14:37 Stephen Rothwell
2019-08-01 22:54 Stephen Rothwell
2019-07-29 21:25 Stephen Rothwell
2019-07-22 21:35 Stephen Rothwell
     [not found] ` <CANP3RGcqGrPnt9eOiAKRbxWVuBkRHRQdWPnANKwrYvtVnTqaSQ@mail.gmail.com>
2019-07-23  0:49   ` Stephen Rothwell
2019-07-03 21:42 Stephen Rothwell
2019-06-30 21:37 Stephen Rothwell
2019-04-22 21:26 Stephen Rothwell
2019-04-23 12:19 ` John Hurley
2019-04-05  5:58 Stephen Rothwell
2019-03-21 18:54 Stephen Rothwell
2019-02-25  8:00 Stephen Rothwell
2019-02-27  1:12 ` tanhuazhong
2019-02-27  2:23   ` Stephen Rothwell
2019-02-27  3:16     ` tanhuazhong
2019-02-11 22:17 Stephen Rothwell
2019-01-31 20:35 Stephen Rothwell

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=20190221053409.GH2736@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=jiri@resnulli.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sbrivio@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.