From: Marius Groeger <mgroeger@sysgo.com>
To: QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Patch submission policy? (was Re: [PATCH] SAMBA multi-share support
Date: Mon, 8 May 2006 20:17:54 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0605082015210.11354@localhost> (raw)
In-Reply-To: <20060508155313.GA15522@jbrown.mylinuxbox.org>
On Mon, 8 May 2006, Jim C. Brown wrote:
> Patches are suppose to be sent to this list. If its a big change, you are
> suppose to split it up into smaller patches and send those (so they can be
> applied one by one).
>
> Beyond that I don't know of any rules.
I learned they should not contain any tabs; one level of indentation
should be 4 spaces.
And of course it should help to have a patch agains head of trunc, not
a past version.
> When patches are ignores, that usually means that it got lost in the mail.
> Thats when you have to get a little bit pushy.
Will need to check this for two of mine, too ... ;->
Cheers
Marius
--
Marius Groeger <mgroeger@sysgo.com>
SYSGO AG Embedded and Real-Time Software
Voice: +49 6136 9948 0 FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.pikeos.com
prev parent reply other threads:[~2006-05-08 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 19:29 [Qemu-devel] Patch submission policy? (was Re: [PATCH] SAMBA multi-share support Stealth Dave
2006-05-08 15:53 ` Jim C. Brown
2006-05-08 18:17 ` Marius Groeger [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=Pine.LNX.4.64.0605082015210.11354@localhost \
--to=mgroeger@sysgo.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).