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 13:17:48 +0100 [thread overview]
Message-ID: <20160826121748.GV13232@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <20160826115653.GA28645@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
On Fri, Aug 26, 2016 at 01:56:53PM +0200, Greg KH wrote:
> On Fri, Aug 26, 2016 at 12:42:05PM +0100, James Hogan wrote:
> > FWIW I have a git alias that blames a git diff or commit (I think based
> > on an old version of [1] with some fixes). That doesn't necessarily tell
> > you where a problem was introduced, but it sure can help if the problem
> > was introduced nearby the fix (and for fixup commits before a rebase).
> >
> > Food for thought if nothing else.
> >
> > E.g.
> >
> > $ git blame-show v4.8-rc2
> > commit 694d0d0bb2030d2e36df73e2d23d5770511dbc8d
> > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > AuthorDate: Sun Aug 14 19:11:36 2016 -0700
> > Commit: Linus Torvalds <torvalds@linux-foundation.org>
> > CommitDate: Sun Aug 14 19:11:36 2016 -0700
> >
> > Linux 4.8-rc2
> >
> > diff --git a/Makefile b/Makefile
> > index 8c504f324154..5c18baad7218 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -1,7 +1,7 @@
> > Blaming lines: 0% (7/1684), done.
> > Blaming lines: 0% (7/1684), done.
> > c517d838eb7d0 (Linus Torvalds VERSION = 4
> > 29b4817d4018d (Linus Torvalds PATCHLEVEL = 8
> > 55922c9d1b84b (Linus Torvalds SUBLEVEL = 0
> > - 29b4817d4018d (Linus Torvalds -EXTRAVERSION = -rc1
> > + 694d0d0bb2030 (Linus Torvalds +EXTRAVERSION = -rc2
> > 1a695a905c185 (Linus Torvalds NAME = Psychotic Stoned Sheep
> > ^1da177e4c3f4 (Linus Torvalds
> > ^1da177e4c3f4 (Linus Torvalds # *DOCUMENTATION*
> >
> > Cheers
> > James
> >
> > [1] https://github.com/dmnd/git-diff-blame/blob/master/git-diff-blame
>
> Oooh, nice! Care to push this "upstream" to get it merged into git for
> everyone to use? It looks helpful to me.
I wasn't planning to, mainly because I'm not the author and presumed
it'd need rewriting to work properly/efficiently with git rather than
just being a wrapper script.
I'd love to see that functionality in git though, maybe as a --blame
argument to git diff/show
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-26 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 4:46 [Ksummit-discuss] Self nomination - Sasha Levin Levin, Alexander
2016-08-26 11:26 ` Greg KH
2016-08-26 11:42 ` James Hogan
2016-08-26 11:50 ` James Hogan
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 [this message]
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=20160826121748.GV13232@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 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.