From: Jerone Young <jyoung5@us.ibm.com>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Perferred way for Patch Submission (inline or attchment)?
Date: Sun, 20 Mar 2005 00:09:01 -0600 [thread overview]
Message-ID: <1111298941.22778.0.camel@thinkpad> (raw)
I'm wondering do you guys prefer we submit patches as attachments or
inline them in the email? Inline in emails have become the standard
everywhere else, what is the preferred way you guys would like patches
submitted to the list.... inline or attachments?
--
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-20 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 6:09 Jerone Young [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-20 10:30 Perferred way for Patch Submission (inline or attchment)? Ian Pratt
2005-03-20 19:54 ` Kip Macy
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=1111298941.22778.0.camel@thinkpad \
--to=jyoung5@us.ibm.com \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.