From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] How to send a sigle git patch which is too big (about 290k) to buildroot
Date: Thu, 08 Jul 2010 12:07:42 +0200 [thread overview]
Message-ID: <87tyoa2snl.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <C83D7CE8356557448A893798C8F9931D05C831F9@frimb01.corp.atmel.com> (Josh Wu's message of "Thu, 8 Jul 2010 11:47:42 +0200")
>>>>> "Wu" == Wu, Josh <Josh.wu@atmel.com> writes:
Wu> Hi,
Wu> I try to send a patch which includes Atmel AT91 Linux and
Wu> experimental patches for Linux Kernel 2.6.30. I paste the patch in
Wu> the end of the email. So the email is too big to send. Can anyone
Wu> tell me what I should do?
It's pretty uncommon for patches to be this big, but I've approved the
mail this time. In the future if you have such big patches (that cannot
be splitted up) you can perhaps put it online somewhere and send a link
instead?
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2010-07-08 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 9:47 [Buildroot] How to send a sigle git patch which is too big (about 290k) to buildroot Wu, Josh
2010-07-08 10:07 ` Peter Korsgaard [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=87tyoa2snl.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox