From: Eli Zaretskii <eliz@gnu.org>
To: jeremy.bennett@embecosm.com
Cc: gdb-patches@sourceware.org
Subject: Re: How to submit a LARGE patch
Date: Sat, 20 Sep 2008 11:36:00 -0000 [thread overview]
Message-ID: <ur67foxs8.fsf@gnu.org> (raw)
In-Reply-To: <1221909745.2827.456.camel@thomas>
> From: Jeremy Bennett <jeremy.bennett@embecosm.com>
> Date: Sat, 20 Sep 2008 12:22:25 +0100
>
> How do I submit a LARGE patch to this group.
My own preference is to submit is as text, not as binary attachment.
Unless your mailer does all kinds of dirty tricks with text, such as
folding long lines etc., this makes reviewing the patch by far the
easiest.
> 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.
How large it is before gzip?
> 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).
It doesn't matter, at least not to me. The information about the
directory is included in the diffs, so applying them correctly is
easy.
next prev parent reply other threads:[~2008-09-20 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 11:23 Jeremy Bennett
2008-09-20 11:36 ` Eli Zaretskii [this message]
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=ur67foxs8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jeremy.bennett@embecosm.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