patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] devtools: fix version search with git < 2.7.0
Date: Fri, 15 Sep 2017 11:24:56 +0200	[thread overview]
Message-ID: <20170915092456.GF2160@autoinstall.dev.6wind.com> (raw)
In-Reply-To: <20170904220532.10175-1-thomas@monjalon.net>

On Tue, Sep 05, 2017 at 12:05:32AM +0200, Thomas Monjalon wrote:
> The script git-log-fixes.sh (used in check-git-log.sh) looks
> for git tags to find the version where a bug is introduced.
> 
> In DPDK 17.08, the script has been fixed to ignore tags from
> non current branch.
> It was using the option --merged which was introduced in git 2.7.0.
> 
> As git 2.7.0 is not so old, a fallback is provided for some years.
> 
> The fallback is replacing the tag --merged option by a branch filter.
> If the tag is found in the branch, the branch name is replaced
> by the tag.
> 
> This script could be improved to allow using another reference branch,
> instead of hard coding HEAD branch (the current one).
> 
> Fixes: 26857dabb3c9 ("devtools: ignore non merged tags for backport")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Tested-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>

Solves the issue.

-- 
Nélio Laranjeiro
6WIND

  reply	other threads:[~2017-09-15  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 22:05 Thomas Monjalon
2017-09-15  9:24 ` Nélio Laranjeiro [this message]
2017-09-22 13:41   ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon

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=20170915092456.GF2160@autoinstall.dev.6wind.com \
    --to=nelio.laranjeiro@6wind.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).