* [Buildroot] How to send a sigle git patch which is too big (about 290k) to buildroot
@ 2010-07-08 9:47 Wu, Josh
2010-07-08 10:07 ` Peter Korsgaard
0 siblings, 1 reply; 2+ messages in thread
From: Wu, Josh @ 2010-07-08 9:47 UTC (permalink / raw)
To: buildroot
Hi,
I try to send a patch which includes Atmel AT91 Linux and experimental patches for Linux Kernel 2.6.30. I paste the patch in the end of the email. So the email is too big to send. Can anyone tell me what I should do?
Thank you.
Best Regards,
Josh Wu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100708/699f4897/attachment.html>
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Buildroot] How to send a sigle git patch which is too big (about 290k) to buildroot
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
0 siblings, 0 replies; 2+ messages in thread
From: Peter Korsgaard @ 2010-07-08 10:07 UTC (permalink / raw)
To: buildroot
>>>>> "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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-07-08 10:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox