From: Linus Torvalds <torvalds@linux-foundation.org>
To: Nick Piggin <npiggin@suse.de>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
glommer@redhat.com, rjw@sisk.pl
Subject: Re: [patch 0/9] vmalloc fixes and improvements
Date: Sat, 8 Nov 2008 09:37:13 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0811080931540.3468@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20081108054144.GB24308@wotan.suse.de>
On Sat, 8 Nov 2008, Nick Piggin wrote:
>
> I thought when there is no From in the body, then it defaults to the first
> Signed-off-by:
Nope. It defaults to the sender. The first signed-off is _usually_ the
right choice, and you can use that as a sanity double-check, but I really
avoid using it for authorship. We actually did that at one point, and it
was reasonably often seriously screwed up and mis-attributed things.
[ It happened either because the first point in the chain had been some
trivial thing that got picked up without sign-off, or because the patch
had actually gone back-and-forth and the author signed off after testing
or improvements.
The first case has been getting fairly rare as people get so used to
sign-offs, but it still happens. The second case has always been pretty
rare, but I'd still rather have it as a "sanity check" than a "blind
heuristic" ]
Linus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-11-08 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 2:15 npiggin
2008-11-08 2:15 ` [patch 1/9] mm: vmalloc allocator off by one npiggin
2008-11-08 2:15 ` [patch 2/9] mm: vmalloc failure flush fix npiggin
2008-11-08 2:15 ` [patch 3/9] mm: vmalloc search restart fix npiggin
2008-11-08 2:15 ` [patch 4/9] mm: vmalloc tweak failure printk npiggin
2008-11-08 2:15 ` [patch 5/9] mm: vmalloc improve vmallocinfo npiggin
2008-11-08 2:15 ` [patch 6/9] mm: vmalloc guard fix npiggin
2008-11-08 2:15 ` [patch 7/9] mm: vmalloc use mutex for purge npiggin
2008-11-08 2:15 ` [patch 8/9] mm: vmalloc make guard configurable npiggin
2008-11-08 2:15 ` [patch 9/9] mm: vmalloc make lazy unmapping configurable npiggin
2008-11-08 5:13 ` [patch 0/9] vmalloc fixes and improvements Linus Torvalds
2008-11-08 5:41 ` Nick Piggin
2008-11-08 15:00 ` Johannes Weiner
2008-11-09 2:15 ` Nick Piggin
2008-11-08 17:37 ` Linus Torvalds [this message]
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.0811080931540.3468@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=glommer@redhat.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=rjw@sisk.pl \
/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