From: Michael Ellerman <michael@ellerman•id.au>
To: linasvepstas@gmail•com
Cc: mahuja@us•ibm.com, linuxppc-dev@ozlabs•org, lkessler@us•ibm.com,
strosake@us•ibm.com, Arnd Bergmann <arnd@arndb•de>
Subject: Re: [PATCH 3/8] pseries: phyp dump: reserve-release proof-of-concept
Date: Tue, 08 Jan 2008 12:13:57 +1100 [thread overview]
Message-ID: <1199754837.7518.71.camel@concordia> (raw)
In-Reply-To: <3ae3aa420801071649w6a8d3939y176dc389d68f4870@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
On Mon, 2008-01-07 at 18:49 -0600, Linas Vepstas wrote:
> On 07/01/2008, Arnd Bergmann <arnd@arndb•de> wrote:
> > On Tuesday 08 January 2008, Manish Ahuja wrote:
> >
> > > Initial patch for reserving memory in early boot, and freeing it later.
> > > If the previous boot had ended with a crash, the reserved memory would contain
> > > a copy of the crashed kernel data.
> > >
> > > Signed-off-by: Manish Ahuja <mahuja@us•ibm.com>
> > > Signed-off-by: Linas Vepstas <linas@austin•ibm.com>
> >
> > I think the signed-off-by chain needs to be modified. The way it appears,
> > you handled the patch first, then sent it to Linas, who forwarded it
> > to whoever will take the patches from the list.
> > This obviously isn't true, since you are actually the one who is sending
> > out the patches. Moreover, I believe that the linas@austin•ibm.com
> > address is now dead, and shouldn't be used for this any more.
>
> Hmm. I wanted to indicate that the work was done while I was at IBM;
> clearly, no one is going through git and changing old, expired email
> addrs, and so submission based on the old addr seemed appropriate.
>
> I'm taking the Signed-off-by line as a quasi-legal thing: a fancy ID string,
> identifying the author(s), rather than a new way to manage email
> address books.
No one's changing the git history (you can't), but it seems silly to
submit a patch with an address that is already dead. There is a general
expectation that if/when someone finds a bug in the code they can email
the signed-off-by addresses and get a real person.
As far as indicating it was written at IBM, that should be covered by
the copyright notices.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-08 1:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 0:19 [PATCH 3/8] pseries: phyp dump: reserve-release proof-of-concept Manish Ahuja
2008-01-08 0:26 ` Arnd Bergmann
2008-01-08 0:49 ` Linas Vepstas
2008-01-08 1:13 ` Michael Ellerman [this message]
2008-01-08 0:50 ` Manish Ahuja
-- strict thread matches above, loose matches on Subject: below --
2008-01-07 23:45 [PATCH 0/8] pseries: phyp dump: hypervisor-assisted dump Manish Ahuja
2008-01-08 0:25 ` [PATCH 3/8] pseries: phyp dump: reserve-release proof-of-concept Manish Ahuja
2008-01-08 3:16 ` Stephen Rothwell
2008-01-16 4:21 ` Paul Mackerras
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=1199754837.7518.71.camel@concordia \
--to=michael@ellerman$(echo .)id.au \
--cc=arnd@arndb$(echo .)de \
--cc=linasvepstas@gmail$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=lkessler@us$(echo .)ibm.com \
--cc=mahuja@us$(echo .)ibm.com \
--cc=strosake@us$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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