mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Ingo Molnar" <mingo@elte.hu>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: Credit for vsprintk work
Date: Wed, 25 Mar 2009 09:59:43 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0903250944360.3032@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.0903250949420.5675@gandalf.stny.rr.com>



On Wed, 25 Mar 2009, Steven Rostedt wrote:
> 
>  $ git blame lib/vsprintf.c |grep 'Frederic Weisbecker' | wc -l
> 542
> 
> You did a hell of a lot of work on vsprintf.c, and you are still too 
> modest to put in a copyright at the top.

I don't disagree, but "git blame" is _not_ a good way to do this.

At a minimum, use "git blame -w -M" to ignore stuff that was just moved 
and re-indented. but even then, quite frankly, "git blame" doesn't really 
make much sense. If you have

	if (!(flags & LEFT)) {
		while (len < field_width--) {

that turns into

	if (!(spec.flags & LEFT)) {
		while (len < spec.field_width--) {

then blame will count the new lines to the person who did the change, but 
was that really a code change? It was a small re-org.

I picked that example because those particular lines actually go back to 
before even the bitkeeper days - their original author is lost in history. 
It used to look different (field_width was called 'size' back in the 
days), but the logic of the code may well go back to the original code by 
Lasu in 1991.

The only point here? Don't use "git blame" as a copyright assigner.

			Linus

  parent reply	other threads:[~2009-03-25 17:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 13:58 Steven Rostedt
2009-03-25 14:18 ` Steven Rostedt
2009-03-25 15:27   ` Ingo Molnar
2009-03-25 16:59 ` Linus Torvalds [this message]
2009-03-25 17:17   ` Steven Rostedt
2009-03-25 19:24 ` Frederic Weisbecker
2009-03-27  2:41   ` Lai Jiangshan

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=alpine.LFD.2.00.0903250944360.3032@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®