Re: [libunwind] x86-64 patch for libunwind v0.97

[David Mosberger]

In order to better track the origin/path of contributions, I think it
makes sense to adopt the "signed-off" procedure that is being used in
the Linux kernel now.  This is a very light-weight procedure which
simply requires reading & understanding the attached text and then
signing off your contribution with:

        Signed-off-by: Random J Developer <address@hidden>

before sending me the patch.

At this point, you don't have to do anything, Max.  I'll review your
patch and if it's in good shape, I'll ask you to retransmit the patch
with the "Signed-off-by" signature attached.  If I have some
feedback/suggestions for improvements, you can make the revisions
first and then send me the revised patch with signature.

Does this sound reasonable?

        --david

-------------------------------------------------------------------
11) Sign your work

To improve tracking of who did what, especially with patches that can
percolate to their final resting place in the kernel through several
layers of maintainers, we've introduced a "sign-off" procedure on
patches that are being emailed around.

The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to
pass it on as a open-source patch.  The rules are pretty simple: if you
can certify the below:

        Developer's Certificate of Origin 1.0

        By making a contribution to this project, I certify that:

        (a) The contribution was created in whole or in part by me and I
            have the right to submit it under the open source license
            indicated in the file; or

        (b) The contribution is based upon previous work that, to the best
            of my knowledge, is covered under an appropriate open source
            license and I have the right under that license to submit that
            work with modifications, whether created in whole or in part
            by me, under the same open source license (unless I am
            permitted to submit under a different license), as indicated
            in the file; or

        (c) The contribution was provided directly to me by some other
            person who certified (a), (b) or (c) and I have not modified
            it.

then you just add a line saying

        Signed-off-by: Random J Developer <address@hidden>

Some people also put extra tags at the end.  They'll just be ignored for
now, but you can do this to mark internal company procedures or just
point out some special detail about the sign-off.