From: Neil Horman <nhorman@tuxdriver.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] maximum line size on patch
Date: Wed, 26 Nov 2014 14:57:29 -0500 [thread overview]
Message-ID: <20141126195729.GA7903@hmsreliant.think-freely.org> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D89726865B45@IRSMSX107.ger.corp.intel.com>
On Wed, Nov 26, 2014 at 05:31:12PM +0000, De Lara Guarch, Pablo wrote:
> Hi,
>
> I am trying to send a patch for new sample app UG, but the patch cannot be sent because I am hitting the maximum line size on the patch.
>
> fatal: /tmp/35JFqgAmCA/0001-doc-Added-new-sample-app-UG-for-VM-power-management.patch: 29: patch contains a line longer than 998 characters
>
> This is due to the included svg files. Is there any way I can include them on the patch? Any other way?
>
You can also just put your local git tree in a public place and send a pull
request to the list.
Neil
> Thanks,
> Pablo
>
prev parent reply other threads:[~2014-11-26 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 17:31 De Lara Guarch, Pablo
2014-11-26 18:12 ` Thomas Monjalon
2014-11-26 19:57 ` Neil Horman [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=20141126195729.GA7903@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
/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).