From: James Hogan <james.hogan@imgtec.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
"Levin, Alexander" <alexander.levin@verizon.com>
Subject: Re: [Ksummit-discuss] Self nomination - Sasha Levin
Date: Fri, 26 Aug 2016 12:50:22 +0100 [thread overview]
Message-ID: <20160826115022.GU13232@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <20160826114205.GA16682@jhogan-linux.le.imgtec.org>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
On Fri, Aug 26, 2016 at 12:42:05PM +0100, James Hogan wrote:
> On Fri, Aug 26, 2016 at 01:26:35PM +0200, Greg KH wrote:
> > On Fri, Aug 26, 2016 at 12:46:51AM -0400, Levin, Alexander wrote:
> > > - Improving tagging for stable. The "version tag" option is broken
> > > and the "Fixes:" tag is always preferable, how do we get people to
> > > use that more often? (script it somehow?
> > > scripts/find-version-it-fixes ?).
> >
> > Oh a script like that would be nice, but how would that work in reality?
>
> Not all Fixes: tags are suitable for stable though. I've been caught out
> by patches being applied to stable (4.2 maybe) due to a Fixes tag,
> without prerequisite patches being applied.
I also find the following alias useful to find the version number a
commit is first merged in:
vc = "!vc() { for i in `git tag --contains \"$@\" | grep '^v'`; do echo \"$(git log -1 --pretty='%ct' $i) $i\"; done | sort -n | head -n1 | sed 's/^[0-9]* //g'; }; vc"
Its a bit slow and hacky and there's probably better ways, but it picks
the tag a bit more reliably than "git describe --contains". Maybe that
could be wrapped in a script that generates a Stable tag automatically
from a Fixes tag for when the patch is suitable for stable.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-26 11:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 4:46 Levin, Alexander
2016-08-26 11:26 ` Greg KH
2016-08-26 11:42 ` James Hogan
2016-08-26 11:50 ` James Hogan [this message]
2016-08-26 12:27 ` Jani Nikula
2016-08-26 12:39 ` James Hogan
2016-08-26 11:56 ` Greg KH
2016-08-26 12:17 ` James Hogan
2016-08-26 13:44 ` Levin, Alexander
2016-08-26 11:48 ` Julia Lawall
2016-08-26 11:55 ` Julia Lawall
2016-08-26 12:11 ` Greg KH
2016-08-26 13:51 ` Levin, Alexander
2016-08-26 13:55 ` Julia Lawall
2016-08-26 18:52 ` Levin, Alexander
2016-08-26 19:59 ` Julia Lawall
2016-08-26 12:08 ` Julia Lawall
2016-08-26 18:55 ` Levin, Alexander
2016-08-26 13:39 ` Levin, Alexander
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=20160826115022.GU13232@jhogan-linux.le.imgtec.org \
--to=james.hogan@imgtec.com \
--cc=alexander.levin@verizon.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.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