From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Ivo Calado <ivocalado@embedded.ufcg.edu.br>
Cc: Jarek Poplawski <jarkao2@gmail.com>,
dccp@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCHv2 1/4] First Patch on TFRC-SP. Copy base files from TFRC
Date: Tue, 13 Oct 2009 15:42:32 -0300 [thread overview]
Message-ID: <20091013184232.GF21809@ghostprotocols.net> (raw)
In-Reply-To: <cb00fa210910131125m17eca24cx4a912e75f91f0fd2@mail.gmail.com>
Em Tue, Oct 13, 2009 at 03:25:48PM -0300, Ivo Calado escreveu:
> strange! I'm using the current DCCP test tree, branch dccp.
> Am I correct in use these rules?
Follow the rules in the latest Documentation/SubmittingPatches file,
that is:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/SubmittingPatches;hb=HEAD
And that states:
-------------------------------------------------------------------
8) E-mail size.
When sending patches to Linus, always follow step #7.
Large changes are not appropriate for mailing lists, and some
maintainers. If your patch, uncompressed, exceeds 300 kB in size,
it is preferred that you store your patch on an Internet-accessible
server, and provide instead a URL (link) pointing to your patch.
-------------------------------------------------------------------
As Jarek pointed out.
- Arnaldo
next prev parent reply other threads:[~2009-10-13 18:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 18:28 [PATCH 1/5] First Patch on TFRC-SP. Copy base files from TFRC Ivo Calado
2009-09-12 18:32 ` Gerrit Renker
2009-09-15 0:38 ` Ivo Calado
2009-09-15 5:25 ` Ian McDonald
2009-09-18 22:54 ` gerrit
2009-09-19 6:16 ` gerrit
2009-10-13 17:18 ` [PATCHv2 1/4] " Ivo Calado
2009-10-13 18:06 ` Jarek Poplawski
2009-10-13 18:12 ` Ivo Calado
2009-10-13 18:21 ` Jarek Poplawski
2009-10-13 18:25 ` Ivo Calado
2009-10-13 18:42 ` Arnaldo Carvalho de Melo [this message]
2009-10-13 18:53 ` Jarek Poplawski
2009-10-19 5:21 ` Gerrit Renker
2009-10-20 13:51 ` Ivo Calado
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=20091013184232.GF21809@ghostprotocols.net \
--to=acme@redhat.com \
--cc=dccp@vger.kernel.org \
--cc=ivocalado@embedded.ufcg.edu.br \
--cc=jarkao2@gmail.com \
--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 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).