From: Rob Earhart <earhart@google.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Submitting a change...?
Date: Mon, 8 Mar 2010 14:38:34 -0800 [thread overview]
Message-ID: <377f3a9b1003081438y25427497j199be53d44075525@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
So, I have a patch I'd like to submit. It's pretty simple - when using a
differencing disk and loading a snapshot, it includes the backing disks in
the search. It seems to work fine on my machine.
I'm not sure what the procedure for submitting changes is; it's been a long
time since I've contributed to an open source project. I used "git clone"
to pull down the source and make my modifications; "git diff HEAD" appears
to be reasonable, "git commit --dry-run" appears to correctly identify the
modified files... but I don't know what comes next. :-)
So now what? Would running "git commit" do the right thing? Should I
generate a diff and send the output somewhere for review and possible
approval? Something else?
Thanks,
)Rob
[-- Attachment #2: Type: text/html, Size: 903 bytes --]
next reply other threads:[~2010-03-08 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 22:38 Rob Earhart [this message]
2010-03-08 23:40 ` [Qemu-devel] Submitting a change...? Alexander Graf
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=377f3a9b1003081438y25427497j199be53d44075525@mail.gmail.com \
--to=earhart@google.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).