From: Jeremy Bennett <jeremy.bennett@embecosm.com>
To: gdb-patches@sourceware.org
Subject: How to submit a LARGE patch
Date: Sat, 20 Sep 2008 11:23:00 -0000 [thread overview]
Message-ID: <1221909745.2827.456.camel@thomas> (raw)
How do I submit a LARGE patch to this group.
I've made some suggested changes to the GDB Internals manual, but since
the change includes an image, the diff file is nearly 300k, when gzipped
and uuencoded. I tried posting it yesterday, but since it hasn't
appeared, I presume there is a size limit.
It's not a particularly large image, but Texinfo requires lots of
flavours (EPS, PDF, PNG, TXT as well as the SVG source it all came
from), so the file gets big.
Second question. When I create the diff file from the patch, is that
expected to be relative to the main source tree, or just the directory
containing the changes (in this case the gdb/doc directory).
Advice appreciated.
Thanks,
Jeremy
--
Tel: +44 (1202) 416955
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com
next reply other threads:[~2008-09-20 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 11:23 Jeremy Bennett [this message]
2008-09-20 11:36 ` Eli Zaretskii
2008-09-20 12:16 ` Jeremy Bennett
2008-09-20 13:22 ` Eli Zaretskii
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=1221909745.2827.456.camel@thomas \
--to=jeremy.bennett@embecosm.com \
--cc=gdb-patches@sourceware.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