patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <luca.boccassi@gmail.com>
To: stable@dpdk.org
Cc: ktraynor@redhat.com
Subject: Re: [dpdk-stable] [PATCH stable-scripts] Fix regex to select commit via Fixed line
Date: Fri, 14 Feb 2020 12:47:19 +0000	[thread overview]
Message-ID: <f67e5c460e99042d368237528606535e9086d9e7.camel@gmail.com> (raw)
In-Reply-To: <20200214114840.11810-1-luca.boccassi@gmail.com>

David pointed out that sed -E is not present on certain ancient
distros, so I'll use --regexp-extended instead which is equivalent

On Fri, 2020-02-14 at 11:48 +0000, luca.boccassi@gmail.com wrote:
> From: Luca Boccassi <
> luca.boccassi@microsoft.com
> >
> 
> The regex was not matching very old DPDK versions with letters in
> it, like 1.3.0r0.
> 
> Signed-off-by: Luca Boccassi <
> luca.boccassi@microsoft.com
> >
> ---
> I had one problem, so I used a regex to fix it.
> Now I have two problems.
> 
>  1-import | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/1-import b/1-import
> index 51e4413..b49e228 100755
> --- a/1-import
> +++ b/1-import
> @@ -46,7 +46,7 @@ then
>  			echo $line >> $tmp_list
>  		# Is the patch fixing a commit that was part of this
> stable release?
>  		# If so select it
> -		elif verlte `echo $line | sed "s/.*(\([0-9][0-9].[0-
> 9][0-9]\).*)/\1/"` $stable_release
> +		elif verlte `echo $line | sed -E "s/.*\(([0-9]+.[0-
> 9]+(.\w+)*)(\s\(.*\))*\)/\1/"` $stable_release
>  		then
>  			echo $line >> $tmp_list
>  		# Was the commit (which might be only in a subsequent
> release)
> 
-- 
Kind regards,
Luca Boccassi


  reply	other threads:[~2020-02-14 12:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 11:48 luca.boccassi
2020-02-14 12:47 ` Luca Boccassi [this message]
2020-02-14 12:56   ` David Marchand

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=f67e5c460e99042d368237528606535e9086d9e7.camel@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).