From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Number 1 tip for getting your patch committed
Date: Thu, 21 Jan 2010 07:58:10 -0500 [thread overview]
Message-ID: <4B584F62.1050406@balister.org> (raw)
Follow the commit log message policy at:
http://wiki.openembedded.net/index.php/Commit_log_example
and use git send-email to send the patch to the list. If you do this, it
makes the act of retrieving the patch from patchwork trivial (see
contrib/patchwprk/pw-am.sh).
This leaves you in a position where you can discuss the patch with
someone with commit access and they can easily apply and push the patch.
Thanks,
Philip
next reply other threads:[~2010-01-21 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 12:58 Philip Balister [this message]
2010-01-23 22:06 ` Using `git send-email` (was: Number 1 tip for getting your patch committed) Paul Menzel
2010-01-24 2:54 ` Holger Hans Peter Freyther
2010-01-25 7:32 ` Khem Raj
2010-01-25 13:46 ` Mark Brown
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=4B584F62.1050406@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.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