qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Dinah B <dinahbaum123@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Adopting abandoned patch?
Date: Mon, 27 Feb 2023 09:57:33 +0000	[thread overview]
Message-ID: <874jr7juo5.fsf@linaro.org> (raw)
In-Reply-To: <CAH50XRfsWih++5yoZSx-3L9mzf+vGPRz2Che=_6TAuATphvXbQ@mail.gmail.com>


Dinah B <dinahbaum123@gmail.com> writes:

> Hi,
>
> I'm looking to get more involved in contributing to QEMU. I noticed that there are some issues in the tracker
> where a sample patch has been contributed but never got merged, like a proposal to add multiboot2 support:
> https://gitlab.com/qemu-project/qemu/-/issues/389

I couldn't see a patch attached to the bug report. Is it elsewhere?

>
> Is another dev allowed to "adopt" the patch as-is, with proper attribution to the original dev and drive it to
> completion/merging (there are some features missing)? Or is "starting from scratch" required for legal
> reasons?

It's certainly possible to pick up a patch from someone else and take it
forward. Aside from addressing any review comments I think the minimum
requirement is the authors original Signed-off-by is intact which
asserts they could contribute code to the project.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2023-02-27 10:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27  3:29 Adopting abandoned patch? Dinah B
2023-02-27  9:57 ` Alex Bennée [this message]
2023-02-27 21:23   ` Dinah B
2023-02-27 21:34     ` Dinah B
2023-02-28  8:16       ` Daniel P. Berrangé
2023-02-28 15:12         ` David Woodhouse

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=874jr7juo5.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=dinahbaum123@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).