From: rapier <rapier@psc.edu>
To: netdev@vger.kernel.org
Subject: Question about Patch Submissions
Date: Tue, 18 Nov 2014 14:13:09 -0500 [thread overview]
Message-ID: <546B9A45.9040509@psc.edu> (raw)
I've read the documentation I've been able to find on the patch
submission process. I was hoping to clarify one thing though. When
submitting a patch that spans multiple files and functions is it better
to break the submission down by function or by file?
Thanks for your time,
Chris
next reply other threads:[~2014-11-18 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 19:13 rapier [this message]
2014-11-18 20:21 ` Question about Patch Submissions Cong Wang
2014-11-18 20:39 ` rapier
2014-11-19 1:38 ` Alexei Starovoitov
2014-11-19 21:29 ` rapier
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=546B9A45.9040509@psc.edu \
--to=rapier@psc.edu \
--cc=netdev@vger.kernel.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 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.