From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Bruce Edge <bruce.edge@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: State of gdbsx in xen-4.0-testing.hg and debugger documentation.
Date: Thu, 8 Jul 2010 16:51:07 +0100 [thread overview]
Message-ID: <19509.62443.169165.677514@mariner.uk.xensource.com> (raw)
In-Reply-To: <AANLkTilaBeMVBC4pxei_k6g9h9acziETk9Evd6KYsTm7@mail.gmail.com>
Bruce Edge writes ("Re: [Xen-devel] State of gdbsx in xen-4.0-testing.hg and debugger documentation."):
> Ian, here's an unstable patch:
Thanks. It still didn't apply to xen-unstable because it had had tabs
replaced with spaces, but I fixed it up.
And finally - sorry for not spotting this before - you should submit
your next patch with a Signed-off-by line like this:
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
except with your name and email address. This indicates that you are
certifying the code as suitable (copyright-wise and so on) for
inclusion in Xen. You can find the precise meaning in the Linux
upstream kernel tree (Documentation/SubmittingPatches, copy below).
In this case, and since your patch was so small, I took your messages
to grant the relevant permissions.
Thanks,
Ian.
>From Documentation/SubmittingPatches:
Developer's Certificate of Origin 1.1
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.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
--
prev parent reply other threads:[~2010-07-08 15:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 5:16 State of gdbsx in xen-4.0-testing.hg and debugger documentation Bruce Edge
2010-07-01 14:53 ` Konrad Rzeszutek Wilk
2010-07-01 20:13 ` Mukesh Rathor
2010-07-01 20:47 ` Bruce Edge
2010-07-14 5:29 ` Bruce Edge
2010-07-14 5:37 ` Bruce Edge
2010-07-14 22:35 ` Mukesh Rathor
2010-07-14 21:10 ` Mukesh Rathor
2010-09-28 16:55 ` Bruce Edge
2010-09-29 1:58 ` Mukesh Rathor
2010-07-01 20:48 ` Keir Fraser
2010-07-02 10:45 ` Stefano Stabellini
2010-07-02 16:52 ` Ian Jackson
2010-07-01 21:54 ` Jeremy Fitzhardinge
2010-07-01 22:08 ` Mukesh Rathor
2010-07-14 14:29 ` Bruce Edge
2010-07-14 23:17 ` Mukesh Rathor
2010-07-15 2:18 ` Mukesh Rathor
2010-07-01 23:51 ` Bruce Edge
2010-07-02 6:11 ` Keir Fraser
2010-07-02 13:11 ` Bruce Edge
2010-07-02 16:53 ` Ian Jackson
2010-07-02 22:41 ` Bruce Edge
2010-07-02 23:43 ` [PATCH] " Bruce Edge
2010-07-06 11:57 ` Ian Jackson
2010-07-06 13:37 ` Bruce Edge
2010-07-06 23:40 ` Bruce Edge
2010-07-08 15:51 ` Ian Jackson [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=19509.62443.169165.677514@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=bruce.edge@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).